User interface device for industrial vehicle

ABSTRACT

A processing device comprising a graphical user interface in an industrial vehicle is provided. The processing device comprises a touch screen display that receives touch gesture commands from a vehicle operator, memory storing executable instructions, and a processor in communication with the memory. The processor when executing the executable instructions: defines a plurality of widgets, wherein each widget comprises a visual representation of a current state of an associated function of the vehicle, displays a subset of the plurality of widgets on a portion of the touch screen display defining a plurality of widget spaces, and displays an icon tray on the touch screen display comprising one or more icons, in which at least one of the one or more icons corresponds to a respective one of the plurality of widgets.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/425,099, filed Nov. 22, 2016, which is hereby incorporated byreference in its entirety. This application is related to U.S. patentapplication Ser. No. 15/210,049, entitled “PROCESSING DEVICE HAVING AGRAPHICAL USER INTERFACE FOR INDUSTRIAL VEHICLE,” by Anthony T.Castaneda, et al., filed on Jul. 14, 2016, which claims the benefit ofU.S. Provisional Patent Application Ser. No. 62/193,840, filed on Jul.17, 2015, both of which are hereby incorporated by reference in theirentirety. This application is also related to the followingapplications, all of which are filed concurrently herewith: U.S. patentapplication Ser. No. ______ (Attorney Docket No. CRN 834 PA), entitled“USER INTERFACE DEVICE FOR INDUSTRIAL VEHICLE,” by Jonathan Ochenas, etal.; U.S. patent application Ser. No. ______ (Attorney Docket No. CRN834 PA3), entitled “USER INTERFACE DEVICE FOR INDUSTRIAL VEHICLE,” byJonathan Ochenas, et al.; and U.S. patent application Ser. No. ______(Attorney Docket No. CRN 834 PA4), entitled “USER INTERFACE DEVICE FORINDUSTRIAL VEHICLE,” by Jonathan Ochenas, et al., all of which arehereby incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates to electronic systems for use in anindustrial vehicle that interacts with and presents information to avehicle operator via a graphical user interface.

BACKGROUND OF THE INVENTION

Industrial vehicles, such as forklift trucks and other materialshandling trucks, are often equipped with a user interface that allows avehicle operator to perform a variety of functions, such as accessingand viewing information programmed into the truck, entering newinformation, and viewing images from onboard cameras. When entering oraccessing information, the operator may be required to scroll or clickthrough large amounts of information across multiple screens or scrollthrough numerous options within a menu. In addition, operators workingin cold environments, such as freezers, typically must wear gloves,which increases the difficulty of navigating through multiple screensand menus.

SUMMARY OF THE INVENTION

Various aspects and embodiments of the present disclosure addressvarious technical problems associated with the need for an operator of amaterials handling vehicle to spend excess time scrolling, clicking orreviewing a large amount of information to locate needed information forviewing on a vehicle user interface screen during operation of thevehicle. The present disclosure provides a first technical solutionwhich involves detecting activation of an icon corresponding to a widgetand, in response to detecting activation of the one icon, automaticallymoving the corresponding widget to a designated widget space foroperator use. Hence, an operator need not manually search throughmultiple widgets, find and move the desired widget to a screen displayas the desired widget is automatically moved to the screen uponactivation of the corresponding icon. Another technical solutioninvolves detecting activation of an icon corresponding to a widget and,in response to detecting the activation of the one icon, allowing afirst menu portion of the one widget to be displayed. Hence, an operatormay access a menu portion of the one widget when needed and desired uponactivation of the corresponding icon and inadvertent access to orappearance of the menu portion is prevented when the corresponding iconis not activated. A further technical solution involves changing a stateof a portion of a widget, such as an outline of a widget, upon a vehiclefunction being completed, e.g., a carriage assembly reaching a desiredheight, which is advantageous as this provides an operator with quickand clear confirmation that the vehicle function has been successfullyexecuted. Yet another technical solution involves detecting activationof an icon corresponding to a widget and, in response, moving the widgetto a predefined widget space, moving the widget from the predefinedwidget space in response to an operator command to move the widget awayfrom the widget space and automatically moving the widget back to thepredefined widget space in response to a command related to a vehicleoperation. Such a solution provides a user interface that is flexible soas to allow an operator to move the widget corresponding to an activatedicon away from the predefined widget space when the operator wishes toview another widget for additional information yet automatically returnsthe widget corresponding to the activated icon to the predefined widgetspace in response to a command related to a vehicle operation, therebysaving the operator time as the operator need not manually look and movethe widget corresponding to the activated icon back to the predefinedwidget space. Other technical problems and corresponding solutions areset out herein.

In accordance with a first aspect of the present disclosure, aprocessing device comprising a graphical user interface in an industrialvehicle is provided. The processing device comprises a screen display,such as a touch screen display that receives gesture commands from avehicle operator, memory storing executable instructions, and aprocessor in communication with the memory. The processor when executingthe executable instructions defines a plurality of widgets, in whicheach widget comprises a visual representation of a current state of anassociated function of the industrial vehicle, controls the display ofor causes to be displayed a subset of the plurality of widgets on aportion of the screen display defining a plurality of widget spaces, andcontrols the display of or causes to be displayed an icon tray or iconrow on the screen display comprising one or more icons, in which atleast one of the one or more icons corresponds to a respective one ofthe plurality of widgets.

The processor when executing the executable instructions in an exampleembodiment defines the icon tray as a separate portion of the screendisplay from the plurality of widget spaces, the icon tray being spacedapart from the plurality of widget spaces. The processor when executingthe executable instructions may lock one of the plurality of widgets inposition in a locked widget space upon activation of an iconcorresponding to the one widget. The widget may be spaced away from itscorresponding icon. The processor when executing the executableinstructions may detect the activation of the icon corresponding to theone widget, and in response to detecting the activation, automaticallymove the one widget to the locked widget space and shift the remainingone or more widgets in the subset to the one or more remaining widgetspaces. The processor when executing the executable instructions mayshift a position of one or more of the widgets of the subset on thetouch screen display following detection of a gesture command on thetouch screen display.

The processor when executing the executable instructions may control orcause display of a first menu associated with one of the plurality ofwidgets when the one widget is displayed in one of the plurality ofwidget spaces on the screen display and a first menu portion of the onewidget is activated by the vehicle operator. In some particularembodiments, the first menu may comprise a list, a sidebar, or a scrollwheel, in which a display of options in the first menu may be altered byone of a tap gesture, swipe gesture, a slide gesture, or a rotatinggesture on the touch screen display and in which the options within thefirst menu may be color-coded with a different color. In otherparticular embodiments, the first menu portion of the one widget may beactivated by the vehicle operator touching or selecting the first menuportion. In further particular embodiments, the processor when executingthe executable instructions may define a plurality of sub-menus, eachsub-menu corresponding to a particular option within the first menu, inwhich one sub-menu may be displayed on the screen display after thecorresponding option within the first menu has been selected and asub-menu portion of the one widget is activated.

The processor when executing the executable instructions may furthercolor code at least a portion of the one sub-menu using a same colorassociated with the corresponding option within the first menu. In someembodiments, one or more of the first menu or the sub-menus may bedisplayed within the one widget. In other embodiments, one or more ofthe first menu or the sub-menus may be displayed in a separate windowthat is temporarily superimposed over one or more of the widget spaces.In further embodiments, the processor when executing the executableinstructions may define the one widget as a rack height select (RHS)widget, the RHS widget comprising a workspace zone menu defining thefirst menu, in which the workspace zone menu comprises a plurality ofworkspace zones, each workspace zone having a corresponding sub-menucomprising a plurality of stored rack heights associated with theworkspace zone. It is also contemplated that the first menu may compriseparameters or categories other than the zone. For example, the firstmenu may comprise a listing of racks designated by type, name and/ornumber. In some particular embodiments, at least a portion of a visualdepiction of each workspace zone comprises a different color, and atleast a portion of a visual depiction of each corresponding sub-menucomprises a same color as the associated workspace zone.

The processor when executing the executable instructions may define oneof the plurality of widgets as a rack height select (RHS) widgetcomprising a workspace zone selection portion defining a first menuportion, in which a rack height selection portion defines a sub-menuportion, and a load presence indicator. In some particular embodiments,the processor when executing the executable instructions may control orcause display of the RHS widget in one of the widget spaces, detect aselection of a particular workspace zone and a particular stored rackheight related to the particular workspace zone, in which after theselection of the particular workspace zone and the particular storedrack height, the workspace zone selection portion comprises anidentifier of the particular workspace zone selected, the rack heightselection portion comprises an identifier of the particular stored rackheight selected, and the load presence indicator comprises a visualindication of a presence or an absence of a detected load. In otherparticular embodiments, the processor when executing the executableinstructions may override the indication of the absence of a detectedload upon activation of the load presence indicator by the vehicleoperator.

In some embodiments, the processing device may further comprise avehicle network system connecting the processor to at least one vehiclenetwork bus, in which the processor extracts a current position of acarriage assembly and a current sensed load weight. The processor whenexecuting the executable instructions may define one of the plurality ofwidgets as a capacity data monitoring (CDM) widget comprising a visualrepresentation of the current position of the carriage assembly and thecurrent sensed load weight.

The processing device may further comprise a vehicle operator controlsection comprising one or more physical input control elements, in whichthe one or more physical input control elements are used to makeselections on the screen display. In some particular embodiments, theone or more physical input control elements may comprise at least one ofa five-button control, a rotary control knob, a trigger switch on amultifunction control handle, or a trigger switch on an armrest.

The processor when executing the executable instructions may determineif a speed of the vehicle is below a threshold speed, and change one ormore of the widgets of the subset on the touch screen display followingdetection of a gesture command on the touch screen display and if thespeed of the vehicle is below the threshold speed.

The processor when executing the executable instructions may move one ofthe plurality of widgets to a predefined widget space upon activation ofan icon corresponding to the one widget.

In accordance with a second aspect of the present disclosure, aprocessing device comprising a graphical user interface is provided. Theprocessing device comprises a screen display, memory storing executableinstructions, and a processor in communication with the memory. Theprocessor when executing the executable instructions defines a pluralityof widgets, in which each widget comprises a visual representation of acurrent state of an associated function, controls or causes display of asubset of the plurality of widgets on a portion of the screen displaydefining a plurality of widget spaces, controls or causes display of anicon tray on the screen display comprising one or more icons, in whichat least one of the one or more icons corresponds to a respective one ofthe plurality of widgets, detects activation of the one of the one ormore icons corresponding to the one widget, and in response to detectingthe activation of the one icon, locks the respective one widget inposition in one of the widget spaces.

The processor when executing the executable instructions may, inresponse to detecting the activation of the one icon, automatically movethe one widget to the locked widget space and shift the remaining one ormore widgets in the subset to the one or more remaining widget spaces.

In accordance with a third aspect of the present disclosure, aprocessing device comprising a graphical user interface in an industrialvehicle is provided. The processing device comprises a screen display,memory storing executable instructions, and a processor in communicationwith the memory. The processor when executing the executableinstructions defines one or more widgets each comprising a visualrepresentation of a current state of an associated function of theindustrial vehicle, controls or causes display of at least one of theone or more widgets on a portion of the screen display defining one ormore widget spaces, controls or causes display of an icon tray on thescreen display comprising one or more icons, in which at least one ofthe one or more icons corresponds to a respective one of the one or morewidgets, detects activation of the one icon corresponding to the onewidget, in response to detecting the activation of the one icon, allowsa first menu portion of the one widget to be displayed, controls orcauses display of a first menu associated with the one widget.

In an embodiment, the processor when executing the executableinstructions may, in response to detecting the activation of the oneicon, allow a first menu portion of the one widget to be activated,detect activation of the first menu portion, and, in response todetecting the activation of the first menu portion, control or causedisplay of the first menu associated with the one widget.

The processor when executing the executable instructions may, further inresponse to detecting the activation of the one icon, lock the onewidget in position in a first widget space on the screen display.

In accordance with a fourth aspect of the present invention, aprocessing device comprising a graphical user interface in an industrialvehicle is provided. The processing device comprises a screen display,memory storing executable instructions, and a processor in communicationwith the memory. The processor when executing the executableinstructions defines one or more widgets, each widget comprising avisual representation of a current state of an associated function ofthe industrial vehicle, and controls or causes display of a rack heightselect (RHS) widget on a portion of the screen display defining one ormore widget spaces, in which the RHS widget comprises a portion thatchanges state upon a related vehicle function being completed, e.g., acarriage assembly reaching a desired height. The outline of the RHSwidget, defining the portion, may become one of darker, wider or bothdarker and wider upon a related vehicle function being completed, e.g.,a carriage assembly reaching a desired height.

In accordance with a fifth aspect of the present invention, a processingdevice comprising a graphical user interface in an industrial vehicle isprovided. The processing device comprises a screen display, memorystoring executable instructions, and a processor in communication withthe memory. The processor when executing the executable instructionsdefines a plurality of widgets, in which each widget comprises a visualrepresentation of a current state of an associated function of theindustrial vehicle, controls or causes display of a subset of theplurality of widgets on a portion of the screen display defining aplurality of widget spaces, controls or causes display of an icon trayon the screen display comprising one or more icons, in which at leastone of the one or more icons corresponds to a respective one of theplurality of widgets, detects activation of the one of the one or moreicons corresponding to the one widget. The processor when executing theexecutable instructions, in response to detecting the activation of theone icon, moves the respective one widget to a predefined widget space,moves the respective one widget from the predefined widget space inresponse to an operator command, and moves the one widget back to thepredefined widget space in response to a command related to a vehicleoperation.

The command related to a vehicle operation may comprise one of a commandto activate a traction motor to effect vehicle movement or a command tolift or lower a carriage assembly.

BRIEF DESCRIPTION OF THE DRAWINGS

While the specification concludes with claims particularly pointing outand distinctly claiming the present invention, it is believed that thepresent invention will be better understood from the followingdescription in conjunction with the accompanying Drawing Figures, inwhich like reference numerals identify like elements, and wherein:

FIG. 1A is a perspective view of an industrial vehicle in accordancewith principles of the present disclosure;

FIG. 1B is a top view of an operator's compartment of an industrialvehicle in accordance with principles of the present disclosure;

FIG. 2A is a block diagram of an industrial vehicle computing enterprisein accordance with principles of the present disclosure;

FIG. 2B is a block diagram of a special purpose processing device on anindustrial vehicle in accordance with principles of the presentdisclosure;

FIG. 3 is an illustration of the processing device of FIG. 2B,implemented as a graphical user interface having a touch screen displayand a corresponding vehicle operator control section in accordance withprinciples of the present disclosure;

FIG. 4 is a block diagram of operational modules executed by a processorof the special purpose processing device of FIG. 2B in accordance withprinciples of the present disclosure;

FIG. 5 is a schematic diagram illustrating an array of widgets fordisplay on a display screen of the processing device of FIG. 3 inaccordance with principles of the present disclosure;

FIGS. 6A and 6B are schematic screen shots of the display screen of theprocessing device of FIG. 3 in accordance with principles of the presentdisclosure;

FIGS. 7A-7I are schematic screen shots of the display screen of theprocessing device of FIG. 3 in accordance with principles of the presentdisclosure;

FIGS. 8-11 are flowcharts of exemplary computer-implemented processesfor defining and controlling display of one or more items on a displayscreen of a display and processing device, in accordance with principlesof the present disclosure; and

FIG. 12 is a block diagram of a computer processing system capable ofimplementing any of the systems, modules, or methods described herein,in accordance with principles of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description of the preferred embodiments,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration, and not by way oflimitation, specific preferred embodiments in which the invention may bepracticed. It is to be understood that other embodiments may be utilizedand that changes may be made without departing from the spirit and scopeof the present invention.

With reference to FIGS. 1A and 1B, an exemplary industrial vehicle 100(hereinafter “vehicle”) is shown. While the present disclosure is madewith reference to the illustrated vehicle 100, which comprises a reachtruck, it will be apparent to those of skill in the art that the vehicle100 may comprise a variety of other industrial vehicles, such as a stockpicker, a turret truck, a tow tractor, a rider pallet truck, a walkiestacker truck, a counterbalance forklift truck, etc. and the followingdescription of the invention with reference to the figures should not belimited to a reach truck unless otherwise specified. The vehicle 100comprises a main body or power unit 112 and one or more wheels,including a pair of fork-side first wheels 160A, 160B coupled to a pairof outriggers 180A, 180B (only one first wheel 160A and one outrigger180A are shown in FIG. 1A) and a powered and steered second wheel 120located underneath a frame 114 of the power unit 112. An overhead guard130 comprises one or more vertically extending supports, such as supportstructures 132A, 132B, affixed to the frame 114, see FIG. 1A, structure132B is not shown in FIG. 1B.

The vehicle 100 further comprises a load handling assembly 140, whichgenerally comprises a mast assembly 142 and a carriage assembly 144. Themast assembly 142 is positioned between the outriggers 180A, 180B andmay comprise, for example, a fixed mast member 146 affixed to the frame114 and nested first and second movable mast members 148, 150. It isnoted that the vehicle 100 may comprise additional or fewer movable mastmembers than the two members 148, 150 shown in FIG. 1A. The carriageassembly 144 may comprise, for example, a lifting carriage (not shown)vertically movable along the mast assembly 142, a fork carriage assembly154 coupled to the lifting carriage for vertical movement with thelifting carriage and a fork structure coupled to the fork carriageassembly 154 comprising a pair of forks 156A, 156B (only one fork 156Ais shown in FIG. 1A) for carrying a load 116, such as a loaded pallet.The fork carriage assembly 154 may comprise a base carriage (not shown)coupled to the lifting carriage and a support carriage (not shown)coupled to the base carriage, which is moveable laterally and may alsopivot relative to the base carriage. The forks 156A, 156B are coupled tothe support carriage. The carriage assembly 144 is movable generallyvertically along the mast assembly 142 and may further comprise a reachassembly (not shown) positioned between the lifting carriage and thefork carriage assembly 154 for horizontally extending the fork carriageassembly 154 away from and toward the mast assembly 142.

A battery (not shown), which is housed in a compartment within the frame114, supplies power to a traction motor (not shown) that is connected tothe second wheel 120 and to one or more hydraulic motors (not shown).The hydraulic motor(s) supply power to several different systems, suchas one or more hydraulic cylinders (not shown) for effecting generallyvertical movement of the movable mast members 148, 150 relative to thefixed mast member 146 and generally vertical movement of the carriageassembly 144 relative to the second movable mast member 150 of the mastassembly 142, as shown by arrow A in FIG. 1A; generally longitudinalmovement of the reach assembly (commonly referred to as “reach”), asshown by arrow B; generally transverse or lateral movement of thesupport carriage and the forks 156A, 156B relative to the base carriage(commonly referred to as “sideshifting”), as shown by arrow C; andpivotable movement of the support carriage and forks 156A, 156B relativeto the base carriage. Hence, the carriage assembly 144 moves relative tothe second movable mast member 150 and also moves with the first andsecond movable mast members 148, 150 relative to the fixed mast member146. The traction motor and the second wheel 120 define a drivemechanism for effecting movement of the vehicle 100 across a floorsurface.

An operator's compartment 122 is located within the main body 112 forreceiving an operator driving or operating the vehicle 100. Theoperator's compartment 122 comprises a variety of control elementsincluding one or more handles, knobs, levers, switches, buttons,sliders, encoders, and combinations thereof, along with one or moredevices that display information to the operator and/or receive operatorinput. For example, a tiller knob 124 is provided within the operator'scompartment 122 for controlling steering of the vehicle 100. An armrest170 located adjacent to an operator seat 128 comprises a control panel126 for receiving input from the operator. In the embodiment shown inFIGS. 1A and 1B, the control panel 126 on the armrest 170 comprises aplurality of fingertip levers 172 which, in the illustrated embodiment,may control carriage assembly (fork) raise/lower, fork tilt, forksideshifting, fork extend or reach and the like. The control panel 126may also comprise a switch (not labeled) for controlling a traveldirection of the vehicle (forward or backward) and a rotary control knob162 for controlling a rack height select function, e.g., wherein thevehicle is programmed to define a set of fork stop locations for each ofa plurality of rack beam heights in respective storage zones. Thecontrol panel 126 may also comprise one or more dual-axis control leversor a multifunction control handle (not shown) in place of, or inaddition to, the fingertip levers 172. In embodiments in which thecontrol panel 126 comprises levers, the traction motor may be actuatedby depression of a floor pedal (not shown). In a further embodiment, thecontrol panel 126 may include a one-click button or trigger switch (notshown) for controlling a rack height select function. In yet anotherembodiment, where a multifunction control handle (not shown) is used inplace of the fingertip levers 172, a trigger switch may be provided onthe multifunction control handle for controlling a rack height selectfunction. In embodiments in which the control panel 126 comprises amultifunction control handle, the traction motor may be actuated byoperation of the multifunction control handle.

In the embodiment shown in FIG. 1B, the power unit comprises a console138 upon which may be mounted a display and processing unit 151 (alsoreferred to herein as a “display unit”) comprising a screen display 152and a five-button keypad 164 comprising up, down, right, left, and enterbuttons for entering information and commands, navigating through menuson the screen display 152, making selections, etc., as described herein.As described herein, the screen display 152 may be implemented as atouch screen (also referred to herein as a touch screen display). Therotary control knob 162 may be used in addition to, or in place of, oneor more of the functions of the five-button keypad 164. The operator maypress a tilt release lever or button 138A located on the console 138 totilt the display unit 151 toward or away from the operator.

In FIG. 1B, the display and processing unit 151 is depicted as beinglocated in front of the operator's seat 128. However, the display unit151 may be placed at other locations in the operator's compartment 122,so long as the display unit 151 is easily viewed and accessed by theoperator. For example, the display unit 151 may be located in an area166 (shown with dashed lines), which includes a dashboard area adjacentto the console 138. The area 166 also includes an optional extension ofthe console 138 along a right side of the operator's compartment 122.Location of the display unit 151 in the area 166, for example, allowsthe operator easy access to the screen display 152 and the five-buttonkeypad 164 without moving his or her arm from the armrest 170.

In some embodiments, the display unit 151 may be mounted, for example,on one of the support structures 132A, 132B. Some vehicles 100, such asthose designed to operate in cold storage, may include an enclosed cabin(not shown) comprising the operator's compartment 122, and the displayunit 151 may be mounted elsewhere in the operator's compartment 122,such as on one or more additional support structures (not shown). Inother embodiments, the display unit 151 may comprise a separate orstandalone device, such as a tablet or laptop computer. In addition,although the rotary control knob 162 is depicted in FIG. 1B as beinglocated on the armrest 170, the rotary control knob 162 in someembodiments may be located elsewhere within the operator's compartment122, e.g., on the display unit 151 (see FIG. 3).

Turning now to FIG. 2A, a general diagram of an industrial vehiclecomputing enterprise comprising a computer system 200 is illustrated inaccordance with various aspects of the present disclosure. Theillustrated computer system 200 is a special purpose (particular) systemthat operates in a manner that enables industrial vehicles, e.g.,vehicles 100, to communicate wirelessly across a computer enterprise.The computer system 200 comprises a plurality of hardware processingdevices (designated generally by reference numeral 202) that are linkedtogether by one or more networks (designated generally by referencenumeral 204). The networks 204, which may comprise wired or wirelessnetworks, provide communications links between the various processingdevices 202 and may be supported by networking components 206 thatinterconnect the processing devices 202. The networking components 206may comprise, for example, routers, hubs, firewalls, network interfaces,wired or wireless communications links and correspondinginterconnections, cellular stations and corresponding cellularconversion technologies (e.g., to convert between cellular and TCP/IP),etc.

The processing devices 202 may comprise any device capable ofcommunicating over the respective networks 204. In certain contexts androles, the processing device 202 is intended to be mobile (e.g., ahardware-based processing device 202 provided on the vehicles 100). Inthis regard, the vehicles 100 include a processing device 202 that maycommunicate wirelessly to the network 204 to carry out the featuresdescribed herein. Under such circumstances, the vehicles 100 maywirelessly communicate through one or more access points 210 to acorresponding networking component 206. The vehicles 100 may also beequipped with WiFi, cellular, or other suitable technology that allowsthe processing device 202 on the vehicle 100 to communicate directlywith a remote device (e.g., over the network(s) 204).

The illustrative computer system 200 also comprises a hardware server212 (e.g., a web server, a file server, and/or other processing device)that supports an analysis engine 214 and one or more corresponding datasources (designated generally by reference numeral 216). The analysisengine 214 and data sources 216 may provide resources to one or more ofthe processing devices 202, including the processing devices 202installed on the vehicles 100.

With reference to FIG. 2B, an exemplary processing device 202 isdescribed in detail. The processing device 202 is equivalent to, and anexemplary embodiment of, the processing device 202 on the vehicle 100,as shown in FIG. 2A. The processing device 202 in FIG. 2B is a specialpurpose, particular hardware computer, such as a device that mounts toor is otherwise integrated with the vehicle 100. The processing device202 may comprise one or more processors coupled to memory to carry outexecutable instructions stored in the memory. However, the executionenvironment of the processing device 202 is further tied into the nativeelectronics of the vehicle 100, making it a particular machine differentfrom a general purpose computer.

The processing device 202 illustrated in FIG. 2B may be implemented asan information linking device that comprises the necessary circuitry toimplement communication with a remote server (e.g., server 212 in FIG.2A), data and information processing for processing vehicle data, andwired (and optionally wireless) communication to components of thecorresponding vehicle 100 to which the processing device 202 is mounted.In accordance with aspects of the present disclosure, the processingdevice 202 (also referred to as a display and processing device) may beimplemented as a main module 218 and a service module 220, which coupletogether to create an integrated processing device 202, e.g., thedisplay and processing unit 151 (FIG. 3). The service module 220 (whichalso includes a graphical user interface module) is field-replaceableand may comprise part of the display and processing unit 151. Theservice module 220 comprises the screen display 152, the five-buttonkeypad 164, and the graphical user interface module defining anynecessary data processing circuitry. In this regard, the service module220 in conjunction with a control module 226, discussed below, define agraphical user interface for the processing device 202. It is alsocontemplated that the main module 218 and the service module 220 may notbe integral such that the main module 218 is separate from the displayunit 151.

In some embodiments, the processing device 202 is connected to atransceiver 222 for wireless communication. Although a singletransceiver 222 is illustrated in FIG. 2B for convenience, in practice,one or more wireless communication technologies may be provided (e.g.,WiFi, Bluetooth®, and/or cellular). For example, the transceiver 222 maybe able to communicate with a remote server (e.g., server 212 of FIG.2A) via 802.11 across the access points 210 of FIG. 2A. The transceiver222 may also optionally support other wireless communication, such asradio frequency (RF), infrared (IR) or any other suitable technology orcombination of technologies. For example, using a cellular-to-IP bridge(not shown), the transceiver 222 may be able to use a cellular signal tocommunicate directly with a remote server, e.g., a manufacturer server(not shown). The transceiver 222 connects to the processing device 202via a suitable electrical connection 224, e.g., an Ethernet connection.However, the transceiver 222 may connect to the processing device 202using other suitable connections. Alternatively, the transceiver 222 maybe built-in or otherwise integral with the processing device 202.

The processing device 202 also comprises data processing circuitry(illustrated generally as the control module 226) having a processor(μP) coupled to a memory for implementing executable instructions,including the relevant processes, or aspects thereof, as set out anddescribed more fully herein. The control module 226 may also compriseother necessary processing circuitry and software, such as forimplementing a display engine, camera processing engine, data processingengine(s), etc. In this regard, the control module 226 may compriseadditional support circuitry, e.g., video ports, camera ports,input/output ports, etc. Moreover, the memory may comprise memory thatstores processing instructions, as well as memory for data storage,e.g., to implement one or more databases, data stores, registers,arrays, etc. Additionally, the control module 226 implements processessuch as operator login, pre-use inspection checklists, data monitoring,and other features, examples of which are described more fully in U.S.Pat. No. 8,060,400, the entirety of which is hereby incorporated byreference herein.

The processing device 202 may also optionally comprise vehicle powerenabling circuitry 228 to selectively enable or disable the vehicle 100and/or to selectively enable or disable select components or functionsof the vehicle 100. In some embodiments, the vehicle power enablingcircuitry 228 may partially or fully enable the vehicle 100 foroperation, e.g., depending upon a proper operator login, a particularvehicle condition, etc. For example, the vehicle power enablingcircuitry 228 may selectively provide power to components via a suitablepower connection (not shown) or otherwise command certain vehiclecomponents not to respond to vehicle operator control via vehiclemessaging, e.g., across one or more vehicle communication busses.

Still further, the processing device 202 comprises a monitoringinput/output (I/O) module 230 to communicate via wired or wirelessconnection between the control module 226 and one or more peripheraldevices mounted to or otherwise associated with the vehicle 100, such asone or more cameras, sensors, meters, encoders, switches, etc. (notseparately labeled; collectively represented by reference numeral 232).The monitoring I/O module 230 may optionally be connected to otherdevices, e.g., third party devices 234, such as one or more RFIDscanners, displays, meters, bar code scanners, cameras, or other devicesto convey information to the control module 226.

The processing device 202 is coupled to and/or communicates with othervehicle system components via a suitable vehicle network system 236. Thevehicle network system 236 may comprise at least one wired or wirelessnetwork, bus, or other communications capability or combination thereofthat allows electronic components of the vehicle 100 to communicate witheach other. As an example, the vehicle network system 236 may comprise acontroller area network (CAN) bus, ZigBee, Bluetooth®, LocalInterconnect Network (LIN), time-triggered data-bus protocol (TTP),RS422 bus, Ethernet, universal serial bus (USB), other suitablecommunications technology, or combinations thereof.

As will be described more fully herein, utilization of the vehiclenetwork system 236 enables seamless integration of the components of thevehicle 100 with the processing device 202, and in particular, thecontrol module 226. By way of example, the vehicle network system 236enables communication between the control module 226 and a fob (via afob reader 240), a keypad, a card reader, or any other suitable devicefor receiving operator login identification, as well as one or morenative vehicle components, such as a vehicle control module, controllers(e.g., traction controller, hydraulics controller, etc.), modules,devices, bus-enabled sensors, displays, lights, light bars, soundgenerating devices, headsets, microphones, haptic devices, etc.(designated generally by reference numeral 238). The control module 226may also facilitate the communication of information from any electronicperipheral devices 232 or third party devices 234 associated with thevehicle 100 (e.g., via the monitoring I/O module 230) that integratewith and communicate over the vehicle network system 236.

Referring now to FIG. 3, an example display and processing unit 151 isillustrated. As noted above, the display unit 151 can implementfunctions and/or features of the display and processing device 202 ofFIG. 2B. As described herein, the display unit 151 may be used in orwith an industrial vehicle, e.g., vehicle 100, and may be mounted to thepower unit console 138, as noted above, or otherwise integrated with thevehicle 100. It will be apparent to those of skill in the art that thedisplay unit 151 may also be used with other types of vehicles, e.g.,automobiles, etc., and in other non-vehicular settings.

The display unit 151 comprises a housing 304 having a front face 306defining a display section 308 comprising the screen display 152 and avehicle operator control section 310. The screen display 152 within thedisplay section 308 may comprise, for example, an LCD screen, a lightemitting diode (LED) screen, a plasma screen, etc. The screen display152 may comprise any known technology, e.g., a touch screen display, soas to receive and respond to gesture commands, e.g., implemented by theoperator directly touching or tapping the touch screen display 152,pressing against or releasing from the touch screen display 152,swiping, sliding, or rotating a finger along or across the touch screendisplay 152, and performing other touch gesture functions or combinationthereof. The terms “gesture command” and “touch gesture command” alsoinclude gesture commands that do not require direct physical contactwith the screen display 152 such as when an operator moves a fingeradjacent to but spaced a small distance from the touch screen display152 in a swiping, sliding, rotating or other motion.

The vehicle operator control section 310 may comprise one or morephysical input control elements, such as buttons, switches, sliders,encoders, knobs, etc., that are used to receive operator input, e.g.,making selections on the touch screen display 152. One or moremultifunction control handles, keypads, keyboards (not shown), orcombinations thereof may be provided in place of the vehicle operatorcontrol section 310. As shown in FIG. 3, the vehicle operator controlsection 310 comprises the five-button keypad 164 including an updirection button 164A, a right direction button 164B, a left directionbutton 164C, a down direction button 164D, and an enter button 164E. Thevehicle operator control section 310 may optionally comprise one or moreadditional input elements or devices, such as a rotary control knob164F, which may be used in conjunction with or in place of the rotarycontrol knob 162 located on the armrest (see FIG. 1B) and may performsimilar functions.

Referring generally to FIGS. 2B and 3, the control module 226 comprisesa hardware processor coupled to physical memory and is capable ofcarrying out computer-executed processes in a hardware system. In thisregard, the processes, architectures, and organizations described hereinmay be implemented on computer-readable hardware that storesmachine-executable program code, where the program code instructs theprocessor to implement the described features. The processor of thecontrol module 226 executes the program code stored in the memory toimplement a graphical user interface control architecture that transmitsinformation to and receives information from the graphical userinterface module of the service module 220. In particular, the controlmodule 226 provides several distinct control functions that impact themanner in which the service module 220 presents and receives informationvia the touch screen display 152 when interacting with the vehicleoperator. For example, as described herein, the processor of the controlmodule 226 may define one or more widgets and/or one or more icons andmay control or cause the touch screen display 152 to display one or moreof the widgets and/or icons.

With reference to FIG. 4, a logical organization of software code storedin memory that is controlled, read and manipulated by the control module226 to effect control of the service module 220 by the control module226, which modules 220 and 226 define the graphical user interface ofthe processing device 202, is illustrated. The features in FIG. 4 areset out in simplified block diagram form and may be executed by thecontrol module 226 of FIG. 2B (e.g., a microprocessor coupled tomemory), and comprises a graphical user interface (GUI) controllermodule 402 that controls a plurality of sub-algorithms (modules) thataffect the manner in which the processing device 202 (FIG. 2B) interactswith the operator. In this regard, the GUI controller module 402communicates with each sub-algorithm/module and further communicateswith the graphical user interface module of the service module 220 (FIG.2B) to present information to the operator via a display screen, e.g.,the touch screen display 152 (FIG. 3), and to receive information fromthe operator, e.g., via touch/gesture controls received through touchingthe touch screen display 152 and/or interacting with one or morephysical control elements in the vehicle operator control section 310 ofthe display unit 151 (FIG. 3) or the control panel 126 (FIG. 1B).

In embodiments in which the screen display 152 comprises a touch screen,the GUI controller module 402 receives and processes touch gesturecommands when the operator touches the touch screen display 152, such astouch, tap, press, release, swipe, scroll, etc. Received touch gesturecommands may comprise, for example, a first touch gesture commandimplemented as an up swipe gesture command, a second touch gesturecommand implemented as a right swipe gesture command, a third touchgesture command implemented as a left swipe gesture command, a fourthtouch gesture command implemented as a down swipe gesture command, and afifth touch gesture command implemented as a select gesture command(e.g., pressing and releasing, tapping, etc.).

In other embodiments, the GUI controller module 402 receives andprocesses operator input from one or more of the control elements in thevehicle operator control section 310 of the display unit 151 (FIG. 3).The GUI controller module 402 may implement a set of controls thatcomprise hardware control equivalents to the touch gesture commandsrecognized by the touch screen display 152. For example, the GUIcontroller module 402 may process a first control designated as an “up”control (e.g., via the operator pressing the up direction button 164A ofFIG. 3), a second control designated as a “right” control (e.g., via theoperator pressing the right direction button 164B), a third controldesignated as a “left” control (e.g., via the operator pressing the leftdirection button 164C), a fourth control designated as a “down” control(e.g., via the operator pressing the down direction button 164D), and afifth control designated as a “select” control (e.g., via the operatorpressing the enter button 164E). The various controls may also beimplemented on a single input device, e.g., a keypad or a rotary controlknob, or via additional separate control elements.

In this regard, the control module 226 (FIG. 2B), e.g., implemented asthe GUI controller module 402, is communicably connected to the touchscreen display 152 (FIG. 3), as described herein. The control module 226detects interactions with the touch screen display 152 and/or one ormore of the control elements in the vehicle operator control section 310or the rotary control knob 162, 164F. For example, the control module226 maps the up swipe gesture command on the touch screen display 152(e.g., the operator places a finger on the touch screen display 152 andswipes upward) and operation of the down control to a same firstgraphical user interface command. The control module 226 maps the rightswipe gesture command on the touch screen display 152 (e.g., theoperator places a finger on the touch screen display and swipes to theright) and operation of the left control to a same second graphical userinterface command. The control module 226 likewise maps the left swipegesture command on the touch screen display 152 (e.g., the operatorplaces a finger on the touch screen display and swipes to the left) andoperation of the right control to a same third graphical user interfacecommand. The control module 226 also maps the down swipe gesture commandon the touch screen display 152 (e.g., the operator places a finger onthe touch screen display 152 and swipes downward) and operation of theup control to a same fourth graphical user interface command. Thecontrol module 226 yet further maps the select gesture command on thetouch screen display 152 (e.g., touch, press, release, etc.) andoperation of the select control to a same fifth graphical user interfacecommand. These graphical user interface commands may vary in functiondepending upon what is currently being displayed on the display 152,examples of which are described in greater detail herein.

The control module 226 may similarly map operator commands associatedwith the rotary control knob 162, 164F. For example, the control module226 maps rotation of the rotary control knob 162, 164F to the left andoperation of the left control to a same (second) graphical userinterface command. The control module 226 maps rotation of the rotarycontrol knob 162, 164F to the right and operation of the right controlto a same (third) graphical user interface command. The control modulemay map depression of the rotary control knob 162, 164F and operation ofthe select control to a same (fifth) graphical user interface command.

The up and down commands or controls may be used to navigate vertically,e.g., up and down within various menus provided in the screen display152 of the display unit 151 (FIG. 3), as described herein in detail. Theup and down commands or controls may also be used to scroll up and downin an image that is too large to display in its entirety in the area ofthe screen display 152, to increment and decrement a value that theoperator provides as an input, etc. The right and left commands orcontrols may be used to navigate laterally, e.g., to scroll across thewidgets and to expose additional widgets; scroll through, drill into,and back out of multilayer menus; scroll to the right or left of animage that is too large to fit in the area of the screen display 152;modify data entry values, etc. Moreover, a combination of the up anddown commands or controls, as well as the right and left commands orcontrols, may be used to scroll across text or other data that is toolarge to fit in the area of the screen display 152. Operation of the“select” command or control enables the operator to, for example,execute an enter command, select or activate a menu option, accept avalue, trigger an action, clear a message, set or stop a timer, orotherwise interact with the information displayed via the display unit151.

The redundancy of the commands and controls generated by touching thetouch screen display 152, and using the corresponding control elements(e.g., buttons 164A-164E in FIG. 3) in the vehicle operator controlsection 310 facilitates operation of the display unit 151, even in harshenvironments. For example, some operators must wear gloves, such asduring operation in refrigerated areas of a warehouse. Moreover, thepositioning of the buttons 164A-164E in close proximity (e.g., on thesame housing) to the touch screen display 152 facilitates operatorinteraction by keeping the operator consistently focused in a commonarea regardless of interaction with the touch screen display 152 ortactile control elements (e.g., buttons) when interacting with thedisplay unit 151. Thus, in this configuration, the buttons 164A-164E areco-located with, for example, the touch screen display 152.

The GUI controller module 402 also facilitates customization of the userinteraction experience. For example, the GUI controller module 402communicates with a user management module 404 and a system managementmodule 406. A user management module 404 may store personalized settingsthat are passed from the control module 226 (FIG. 2B), such as inresponse to an operator logging into a corresponding vehicle 100 using afob via the fob reader 240 (FIG. 2B), or via logging onto the vehicle100 using the display unit 151. The system management module 406 may beutilized to control the allowable operator-specific settings, e.g., bylimiting, disabling, enabling, etc., features. In an illustrativeexample, the user management module 404 may be used to store a vehicleoperator performance or skill level, a theme preference, a languagepreference, unit measurement preference (e.g., metric or English),widget arrangement, etc. A generic template may be provided where thereis no customization data available for a specific vehicle operator. In afurther illustrative example, the system management module 406 limitsand controls the ability of the vehicle operator to configure themes,language preference, widget arrangement, widget customization, etc. Oneor more of these features may be temporarily overridden or permanentlylocked out, e.g., by a system supervisor, from appearing as a usersettable parameter. For example, the available themes may be set orlimited based upon a vehicle operator level, truck level, company level,etc., and may be temporarily overridden for certain vehicle-specificfunctionality, e.g., to provide an inspection checklist, to providecertain diagnostic information, etc.

The GUI controller module 402 further communicates with a vehiclemanagement module 408. The vehicle management module 408 stores andcontrols information about the specific vehicle 100 on which theprocessing device 202 (FIG. 2B) is installed. For example, the vehiclemanagement module 408 may comprise information about a maximum forkheight, maximum weight, battery charge, or other vehicle-specificcharacteristics.

The GUI controller module 402 still further communicates with a languageformat module 410, which may be used to set a preferred language for thedisplay of text on the screen display 152 (FIG. 3). In particular, thelanguage format module 410 manages the strings that are to be translatedand pushed to the screen display 152, as well as the font, textalignment, direction, and other features that affect readability of thedesired information by the operator. The GUI controller module 402 stillfurther communicates with a communication module 412, which controls thecommunication of the GUI controller module 402 with other vehiclecontrollers, modules, devices, sensors, third party devices, etc., asset out in FIGS. 2A and 2B.

The GUI controller module 402 further communicates with a message systemmodule 414. The message system module 414 may control the messaging thatis presented to the operator, as well as the manner in which themessaging is presented to the operator. For example, a message may bedisplayed across a portion of the screen display 152, e.g., across abottom third, across one widget space (606, 608 in FIG. 6A), or acrossthe entire screen display 152 (FIG. 3). The GUI controller module 402also communicates with a dashboard module 416. The dashboard module 416controls icons, the icon order, widgets, the widget order, and the menusystems that are presented on the screen display 152. The dashboardmodule 416 is also responsible for screen management, e.g., storing thecurrent screen, next screen, previous screen, etc., and for tracking themenus, calibration, checklists, icon display, widget display, messaging,text and video messaging, etc. The GUI controller module 402 furthercommunicates with a user I/O module 418 to translate inputs provided bythe operator into instructions that are interpreted to facilitate avehicle operator interaction experience when interacting with thegraphical user interface module of the service module 220 (FIG. 2B),which may be implemented as part of the display unit 151 (FIG. 3). Forexample, the user I/O module 418 may process input received via touchgesture commands from the operator touching the touch screen display152, via the physical control elements in the vehicle operator controlsection 310 or via the control panel 126 (FIG. 1B).

In accordance with aspects of the present disclosure, the screen display152 may be utilized to display one or more widgets, each of which isdefined by an application program forming part of the dashboard module416 that provides a visual representation on the screen display 152. Inan embodiment, computer instructions are provided in the form of anapplication program stored in memory that instructs the processor of thecontrol module 226 what a particular widget looks like, how it behavesand how it responds to operator actions and/or vehicle-relatedinformation. The visual representation provides information to theoperator and allows the operator to interface with the control module226. For example, widgets may provide visual representations of acurrent state of one or more associated vehicle features, functions, oroperations (e.g., a battery charge, a current vehicle speed, etc.)and/or one or more ancillary conditions (e.g., environmental conditionsuch as the current time). In an exemplary embodiment, widgets may beused to represent the current state of the vehicle speed, fork height,load weight, battery charge, clock, stop watch, odometer, trip meter,hour meter, time, and date.

In this regard, the widgets represent “live” or real-time data. Withreference to FIGS. 2A and 2B, the current state of data values may beobtained, for example, by the processor of the control module 226communicating with (e.g., querying, polling, reading from, etc.) one ormore vehicle control modules, sensors, etc. (e.g., one or moreelectronic peripheral devices 232) across the vehicle network system236, via the monitoring I/O module 230, or a combination thereof. Thecurrent state data may also be ascertained by polling or otherwisequerying a remote server, e.g., the server 212, which extracts relevantdata from the data sources 216, e.g., a vehicle data repository, andcommunicates that relevant data back to the control module 226.Furthermore, the control module 226 may read the current state from adesignated memory on the vehicle 100, e.g., a master state datarepository (not labeled). For example, a process on the vehicle 100(e.g., a process executed by the controller/processor in the controlmodule 226) may be tasked with cyclically collecting and refreshingvehicle state information in the designated memory, e.g., every 100milliseconds or less. The designated memory thus defines a vehicle statelookup table that may be accessed to make decisions based on a currentoperating state of the vehicle 100. The current state data may alsoinclude data regarding the vehicle operator performance or skill level.

By way of example, by continually data logging operator-basedperformance and/or vehicle operation data, one or more of the widgetsmay provide a dashboard view of key vehicle and/or operator performancemeasures. In this regard, the overall data provided in a widget need notbe limited to data collected by or stored in a specific vehicle. In someembodiments, one or more of the widgets may reflect all of the relevantvehicle data associated with the logged in operator, regardless of whichvehicle the operator is currently operating. In other embodiments, oneor more of the widgets may tie into third party databases to displayother information, such as operational information, messages,information from a warehouse management system, feeds (such as fromnews, sports, and weather), etc. Thus, the processing device 202 iscommunicably connected to a communications device (e.g., the transceiver222) such that the processing device 202 receives from a remote server(e.g., the server 212), information that is not extracted from thevehicle 100.

With reference to FIG. 5, the widgets may be organized into an array500. The array 500 dictates, for example, which widgets will bepresented on the screen display 152 (FIG. 3) and the order in which thewidgets will be presented. For example, a first widget 502(1) isdesignated as a leftmost widget, followed by widgets 502(2), 502(3) . .. 502(N), in which N is any reasonable number. The vehicle operator mayadd as many widgets as are available or as are limited via preferencesset in the user management module 404 (FIG. 4). Moreover, the operatormay rearrange the order of presentation of the widgets so that thewidgets are ordered as desired, as described herein. One or morewidgets, e.g., widgets 502(1) and 502(2), may be used to set a “HomeScreen,” which may be displayed as a default or to which the operatormay return. The Home Screen may, for example, display the two widgetsrepresenting the most important features for the operator. The widgetsmay also be configured and ordered from the screen display 152, e.g.,via input from the operator, or the widgets may be set or preset by thesystem supervisor or via a remote computer, which wirelessly sends thewidgets and widget order to the vehicle 100, such as through the remoteserver 212 (FIG. 2A).

Referring now to FIGS. 6A and 6B, an exemplary display screen 600 isillustrated, which may be implemented as a touch screen. The displayscreen 600 is an example of a graphical user interface display, whichmay be presented by the screen display 152 of the display unit 151 (FIG.3). The display screen 600 may be conceptually broken down into severalsections comprising a menu selection section 602, a first docked statustray 604A, a second docked status tray 604B, and one or more widgetspaces, which are illustrated as a first widget space 606 and a secondwidget space 608. Although the display screen 600 is depicted herein ascomprising one menu selection section, two status trays, and two widgetspaces, it will be apparent to those of skill in the art that differentconfigurations of the display screen 600 are possible. For example, theupper portion of the display screen 600 may comprise only one statustray or three or more status trays. In addition, the display screen 600may comprise three or more widget spaces. However, a size of the displayscreen 600 may dictate the number of available widget spaces and/orstatus trays.

As shown in FIG. 6B, the menu selection section 602 may be used toaccess a menu, e.g., a drop down menu 602 a, relating to one or moregeneral vehicle settings and to the general operation and appearance ofthe display screen 600. Selection of one of the options in the drop downmenu 602 a may result in the display of one or more sub-menus (notshown) with additional options related to the selected option. One ormore of the options in the drop-down menu 602 a and/or sub-menu(s) maycomprise an associated number or value (not shown) that may be viewedand/or changed by clicking or selecting on the option. The operator mayaccess the menu 602 a or sub-menu(s) and make selections as describedherein. In some embodiments (not shown), the menu 602 a may be displayedover both widget spaces 606, 608.

One status tray, e.g., the first status tray 604A, or a portion thereofmay be used to display information such as one or more identifiersrelated to the operator, the vehicle, the vehicle owner, etc. One statustray, e.g., the second status tray 604B, or a portion thereof maycomprise an icon row or an icon tray that is used to dock apredetermined number of system status icons (730 in FIG. 7A). The firstand second widget spaces 606, 608 each display a widget comprising avisual representation of a current state of an associated ancillarycondition or vehicle feature or function. The term “a current state ofan associated function of a vehicle” is intended to encompass “thecurrent state of an associated ancillary operation, condition or vehiclefeature or function.” In the exemplary display screen 600 shown in FIGS.6A and 6B, two widgets N-2, N-3 are displayed, e.g., according to theorder set by the array 500 (FIG. 5). Thus, because widget N-2 isdisplayed in the first widget space 606, widget N-3 is displayed in thesecond widget space 608. Moving the widgets to the right would shiftwidget N-2 into the second widget space 608 and a new widget, widgetN-1, into the first widget space 606 (not shown). Likewise, moving thewidgets to the left would shift the widget N-3 into the first widgetspace 606 and widget N-4 into the second widget space 608 (not shown).This process may continue so that the operator may scroll through all ofthe assigned widgets in the array 500. At widget N-1 and N-N, thescrolling may stop or wrap around to the next adjacent widget in thearray 500.

An optional widget position indicator 610 may be utilized to illustratethe number and position of the displayed widgets within the array 500.In the embodiment shown, the widget position indicator 610 comprisescircles, but in other embodiments (not shown) the widget positionindicator 610 may comprise another shape, e.g., squares, triangles, etc.A number of circles 610(1) . . . 610(N) may correspond to a number ofwidgets available within the array 500, see FIGS. 6A and 6B. Forexample, as shown in FIG. 7B, there are nine widgets available fordisplay, as indicated by circles 610(1) to 610(9). In FIGS. 6A and 6B, aportion or subset of the available widgets, e.g., widgets N-2 and N-3,is displayed on the display screen 600, and the widget positionindicator 610 may also indicate a current position of the displayedwidgets N-2, N-3 within the array 500. For example, widgets N-2 and N-3are the second and third widgets in the array, as indicated by thesecond and third circles 610(2), 610(3) in the widget position indicator610 being solid. The remaining widgets, i.e., widgets N-1 and N-4 to N-Nare off the display screen 600, as indicated by the corresponding firstand fourth through Nth circles 610(1), 610(4)-610(N) being open.

With reference to FIGS. 7A-7C, several aspects of the generalfunctionality of the screen display 152 of the display unit 151 (FIG. 3)will be discussed in detail. An exemplary display screen 600, which maybe implemented as a touch screen, is illustrated and may comprise anexample of a graphical user interface display, which may be presented bythe screen display 152. Although reference is made to elements andfeatures of particular icons and widgets, those of skill in the art willappreciate that the described elements and features are not limited tothese particular icons and widgets. In addition, labeling of someelements is omitted for clarity.

As shown in FIG. 7A, display screen 600 is conceptually broken down intoa menu selection section 602, a first status tray 604A, and a secondstatus tray 604B, as represented by the dashed lines. The first statustray 604A comprises one or more identifiers 720, such as the operator'sname, e.g., “J. SMITH,” the name of another person actively logged intothe vehicle, a vehicle name, a company name, a location, etc. The secondstatus tray 604B comprises an icon tray with one or more system statusicons 730. The first widget space 606 comprises a capacity datamonitoring (CDM) widget 740, and the second widget space 608 comprises aspeedometer widget 750. The widget position indicator 610 indicates thatthere are nine widgets available for display and that the CDM andspeedometer widgets 740, 750 are widgets N-1 and N-2 in the associatedarray 500 of widgets (FIG. 5), as indicated by the first and secondcircles 610(1), 610(2) being solid and the remaining circles 610(3) to610(9) being open.

Each icon 730 corresponds to a current state of an associated vehiclefeature, function, or operation or an ancillary condition. For example,the icons 730 depicted in FIG. 7A comprise a rack height select (RHS)icon 730A, a steer wheel/travel direction indicator icon 730B, aperformance icon 730C, a messaging icon 730D, a battery condition icon730E, and a clock icon 730F. In some embodiments, one or more of theicons 730 displayed in the second status tray 604B may be locked orfixed in position on the display screen 600, e.g., in the icon tray, andmay be changed, for example, only by a system supervisor or fleetmanager. For example, in some embodiments, the RHS icon 730A may beactivated or inactivated by the operator, as described herein, but maybe removed or otherwise altered only by the system supervisor or fleetmanager. One or more of the icons 730 may comprise an indicator thatprovides a visual representation of the current state of the associatedvehicle feature, function, or operation or ancillary condition. Forexample, the steer wheel/travel direction indicator icon 730B comprisesan arrow within a circle (not separately labeled) indicating a generalsteer wheel/travel direction within a 360° plane, the messaging icon730D comprises a message bubble with a “1” to indicate that the operatorhas one message, the battery icon 730E displays “86” to indicate thatthe battery charge is currently 86%, etc. Thus, the operator may use theicons 730 to quickly determine the current state of the correspondingvehicle features, functions, or operations or ancillary conditions,without the need to display a corresponding widget in one of the widgetspaces 606, 608.

In some embodiments, at least one of the icons 730 corresponds to arespective one of the widgets. The corresponding widget may be displayedin one of the widget spaces 606, 608, or the corresponding widget may beavailable in the array 500 (FIG. 5) but is currently off the displayscreen 600. For example, as shown in FIGS. 7A and 7B, the RHS icon 730Acorresponds to an RHS widget 760, which is off the screen in FIG. 7A andis displayed in the first widget space 606 in FIG. 7B. Alternatively,the corresponding widget may be installed on the vehicle 100, i.e.,stored in memory, but is not currently in the array 500 of widgetsavailable for display. In a particular embodiment, the last widget inthe array may comprise an “add” widget (not shown) that, when touched orselected, displays a menu as described herein that lists additionalavailable widgets for selection and insertion into the array 500. Inother embodiments, one or more of the icons 730 may not include acorresponding widget. For example, the clock icon 730F may not include acorresponding widget. Each icon may be defined by an application program(similar to the widget application program) forming part of thedashboard module 416 that provides a simple visual representation on thescreen display 152. In an embodiment, computer instructions are providedin the form of an application program stored in memory that instructsthe processor of the control module 226 what a particular icon lookslike, how it behaves and how it responds to operator actions and/orvehicle-related information.

In further embodiments, one or more of the icons 730 may appear onlywhen a particular condition is satisfied or occurs. For example, themessaging icon 730D may appear in the second status tray 604B only uponreceipt of a new message, and a maintenance icon (not shown) may appearonly upon receipt of an indication of a problem with a vehicle componentor system. In yet further embodiments, one or more of the icons 730 maybe removed from the second status tray 604B when a particular conditionis satisfied or occurs.

The performance icon 730C may be used to set a vehicle mode (e.g.,training, economy, or full performance mode).

In some embodiments, selection or activation of one of the icons locksthe corresponding widget into place on the display screen 600 in adesignated or “locked” widget space. As used herein, “activation” isintended to comprise touching, tapping, clicking, or otherwise selectinga portion of the display screen where the icon is located using one ormore touch gestures and/or one or more physical control elements, suchas the physical control elements found in the vehicle operator controlsection 310 (FIG. 3) or the control panel 126 (FIG. 1B), e.g., therotary control knob 162 or trigger switch (not shown). For example, uponthe touch screen 600 sensing an operator touching or tapping thecorresponding portion of the touch screen 600 where the icon is located,the icon becomes activated. The activated icon becomes deactivated whenan operator touches or taps the corresponding portion of the touchscreen 600 where the activated icon is located. The locked widget spacemay comprise any one of the widget spaces, e.g., the first or the secondwidget space 606, 608. The widget corresponding to the activated iconmay already be located in the locked widget space, in which case thecorresponding widget will be locked in place in its current locationupon activation of the icon and, in one embodiment, will not move fromthe locked widget space unless the corresponding icon is deactivated. Ifthree or more widget spaces are provided, the locked widget space maycomprise a center widget space. If none of the icons is activated, anywidget located in the designated or “locked” widget space is not lockedin position.

However, the widget corresponding to the activated icon may be locatedin one of the other widget spaces or may be off the display screen 600.In some embodiments, the widget corresponding to the activated icon maynot be in the array 500 (FIG. 5) of widgets currently available fordisplay on the display screen 600 but is installed on the vehicle 100,i.e., stored in memory. In all cases in which the corresponding widgetis not currently displayed in the locked widget space, the remainingwidgets may be shifted to the right or left to allow the correspondingwidget to move to the locked widget space. In some embodiments, themovement of the corresponding widget and shifting of the remainingwidgets may occur automatically upon detecting activation of the iconsuch that the corresponding widget immediately moves to the lockedwidget space and becomes locked in position. In other embodiments, theremaining widgets will be shifted only upon detection of a touch gestureor actuation of one or more control elements following activation of theicon. In further embodiments, selection of an icon and movement of thecorresponding widget into the locked widget space may automaticallyreorganize the array 500 of widgets to place the widget corresponding tothe selected icon in the first position in the array 500, e.g., thefirst widget 502(1). In yet further embodiments, activation of an iconfor a widget that is not currently in the array 500 and display of thewidget on the display screen 600 upon activation of the correspondingicon may also result in the introduction of an additional circle (notshown) in the widget position indicator 610 to indicate the presence ofthe additional widget.

For example, with reference to FIGS. 7A and 7B, the CDM widget 740 inFIG. 7A is located in the first widget space 606, and the speedometerwidget 750 is located in the second widget space 608. In FIG. 7B, theRHS icon 730A′ has been activated, and the corresponding RHS widget 760has been moved into a locked widget space, e.g., the first widget space606 at the leftmost side of the display screen 600. The remainingwidgets 740, 750 have been shifted to the right, i.e., the CDM widget740 has been shifted into the second widget space 608 in FIG. 7B and thespeedometer widget 750 has been moved off the display screen 600 to theright.

One or more characteristics of a visual appearance of the activated iconmay be altered upon activation. For example, as shown in FIG. 7B, theactivated RHS icon 730A′ is underlined 735. Alternatively, or inaddition to the underlining 735, a box (not shown) may appear around theactivated icon and/or a color or appearance of one or more portions ofthe activated icon may change (not shown). For example, the text “RHS”in the activated RHS icon 730A′ may be changed to italics and/or may bechanged from a default color to another color (e.g., from white toorange upon activation) or a combination thereof to clearly indicate tothe operator that the icon has been activated. In addition, a portion ofthe background of the activated icon may also change color or appearanceupon activation (not shown).

In addition, one or more characteristics of the widget positionindicator 610 may be altered to indicate that a widget has been lockedinto place in the locked widget space. For example, as shown in FIG. 7B,the first circle 610(1)′ in the widget position indicator 610 ischanged, for example, from solid black, as indicated in FIG. 7A, to adifferent color (e.g., orange) to indicate that the corresponding widgethas been locked into place. A background pattern, shape (not shown), orother characteristic of the widget position indicator or combinationsthereof may also be changed to indicate that a widget has been lockedinto place. Where the locked widget space comprises the second widgetspace 608 or another widget space, one or more characteristics of thecorresponding circle 610(2) . . . 610(N) in the widget positionindicator 610 may also be changed (not shown).

Prior to activation of an icon and locking of the corresponding widgetinto the locked widget space, the operator may scroll through thewidgets using one or more touch gestures and/or one or more physicalcontrol elements, as described herein, and the widgets in both widgetspaces will change as the operator cycles through the array 500 (FIG.5). In some embodiments, the operator may change a widget's currentposition in the array 500 by pressing and holding on the widget anddragging and dropping the widget to the desired location (not shown).After activation of an icon and locking of the corresponding widget intothe locked widget space as shown, for example, in FIG. 7B, only thewidgets in the remaining widget space(s) may be changed by scrolling.For example, following activation of the RHS icon 730A′ and locking ofthe RHS widget 760 in the locked (first) widget space 606 in FIG. 7B,the operator scrolls to the left through the remaining widgets, whichgenerates the display screen 600 shown in FIG. 7C. The speedometerwidget 750, which was previously off the display screen 600 to theright, moves back into the second widget space 608. Because the RHSwidget 760 is now locked into place in the first widget space 606, theCDM widget 740 moves off the display screen 600 to the left. In thewidget position indicator 610, the first circle 610(1)′ corresponding tothe RHS widget 760 remains orange. The second circle 610(2), which nowcorresponds to the CDM widget 740 is open, as the CDM widget 740 hasmoved off the display screen 600, and the third circle 610(3), which nowcorresponds to the speedometer widget 750, is solid.

In some embodiments, activation of an icon may move the correspondingwidget to a predefined widget space but does not lock the widget inplace. For example, activation of the RHS icon 730A may cause the RHSwidget 760 to move into a predefined widget space, e.g., the firstwidget space 606 as shown in FIG. 7B, but the operator may then scrollthrough the widgets as before, i.e., the RHS widget 760 may be moved offthe screen (not shown) in response to an operator command to move thewidget. Receipt of an operator command related to a vehicle operationmay cause the corresponding widget to immediately move back to thepredefined widget space. For example, if the operator has moved the RHSwidget 760 off the display screen 600, receipt of a command to activatethe traction motor to effect vehicle movement or receipt of a command tolift or lower the carriage assembly 144 (FIG. 1A) or actuation of thetrigger switch (not shown) may cause the RHS widget 760 to move back tothe first widget space 606. In other embodiments, receipt of an operatorcommand related to a vehicle operation may cause a corresponding widgetto move to a predefined widget space. For example, receipt of a commandto lift or lower the carriage assembly 144 (FIG. 1A) or actuation of thetrigger switch (not shown) may cause the RHS widget 760 to move into thefirst widget space, as shown in FIG. 7B.

In all embodiments, movement of the corresponding widget to a locked ora predefined widget space on the display screen 600 in response to aparticular operator command may save time for the operator and help toincrease productivity, as there is no need for the operator to manuallysearch for the appropriate widget and/or move the widget back onto thedisplay screen 600 if the operator has navigated away from the widget.Thus, the processing device 202 disclosed herein, as implemented, forexample, in the display unit 151, provides a smart and flexible userinterface that ensures that the operator receives the most relevantinformation at the correct time with the least operator input.

In additional embodiments, upon movement of a widget into apredetermined widget space (by scrolling, by activation of thecorresponding icon, etc.), a message (not shown) related to the widgetmay optionally be displayed. If the predetermined widget space is, forexample, the first widget space 606, the message may be temporarilysuperimposed over the second widget space 608 and may appear only when apredefined condition is met. For example, if a battery condition widget(not shown) is moved into the first widget space 606 and the batterycharge is below a certain level, a message, e.g., “Low Battery,” mayappear to alert the operator that the battery may need to be changedsoon. In addition, if the operator moves the speedometer widget 750 intothe first widget space 606, a message, e.g., “Speed Too High,” mayappear if the operator is exceeding a speed limit.

In further embodiments, the control module 226, which is communicablycoupled to one or more vehicle system modules via the vehicle networksystem 236 (FIG. 2B), may extract data related to a current vehiclestate, as described herein, and use this data to alter a display of thewidgets and/or icons on the display screen 600. For example, displayunit 151 (FIG. 3) may be configured to have one or more “home” positionsand/or “home” screens that each display one or more widgets that arerelevant to a current vehicle state or a current task. These featureshelp to ensure that the vehicle operator has ready access to theinformation that is most relevant to the current task without the needto search through all of the widgets available on the vehicle 100, whichmay help to increase operator productivity.

In some particular embodiments, the control module 226 extracts from atraction control module (not shown), directly or via a memory or currentvehicle state lookup table, an indication as to whether the tractioncontrol is engaged. If the current operating state of the tractioncontrol module indicates that the traction controls are engaged, thecontrol module 226 causes the display screen to “snap” back to adesignated “home” position, such as the first two widgets in the array500 (FIG. 5). In addition, when traveling, the display screen 600 mayalso automatically change to a “motion home screen” that shows relevanttravel-related widgets, such as the speedometer widget 750.

In other particular embodiments, the control module 226 extracts from ahydraulic valve control module (not shown) an indication as to whetherthe forks 156A, 156B (FIG. 1A) are engaged in a lift operation on thevehicle 100. Where the current operating state indicates that the forks156A, 156B are engaged in a lift operation, the control module 226causes the display screen 600 to snap to a designated “lift” homeposition or “lift home screen” having relevant widgets, such as the CDMwidget 740 and the RHS widget 760.

In yet further embodiments, the control module 226 may use the extracteddata related to the current vehicle state to selectively disableoperation of one or more portions of the display unit 151. The displayscreen 600 may continue to display the current state of one or morevehicle features, functions, or operations, but the touch layer may befully or partially disabled such that the display screen 600 isunresponsive to touch gesture commands. The control module 226 may alsooptionally disable one or more of the control elements in the vehicleoperator control section 310 (FIG. 3). These features may help to reduceoperator distraction and increase operator productivity by ensuring thatthe vehicle operator remains focused on the current task.

In some particular embodiments, if the current operating state of thetraction control module indicates that the traction controls areengaged, as described herein, the control module 226 may lock thedisplay screen 600 so that the operator cannot scroll through otherwidgets or otherwise leave the home position.

In other particular embodiments, the control module 226 extracts a speedof the vehicle 100 based upon information received from the vehiclenetwork bus, e.g., a vehicle network system 236 (FIG. 2B) andselectively disables one or more portions of the display unit 151. Forexample, all touch gesture commands may be disabled if the controlmodule 226 determines that the vehicle speed is above a threshold speed.When the control module 226 determines that the speed of the vehicle 100is below the threshold speed, the control module 226 may enable fulloperation of the display unit 151, e.g., one or more of the widgetsdisplayed on the display screen 600 may be changed.

In yet further particular embodiments, the display of the icons and/orwidgets on the display screen 600 may be customized based on staticvehicle information, such as a vehicle type (e.g., forklift vs. stockpicker), a vehicle model, etc., and/or one or more operator-basedmetrics, such as a current level of completion of a task (e.g.,percentage of picks per shift), an operator skill or performance level,a level of correct vehicle operation or environmental behaviors, etc.For example, less skilled operators may benefit from the constantdisplay of the icons and/or widgets corresponding to a steerwheel/travel direction 730B and a vehicle speed 750, while more skilledoperators may wish to monitor different vehicle operations and systems.These features help to ensure that the display screen 600 presents eachindividual vehicle operator with the relevant and useful information.

With reference to FIGS. 7A-7I, several features of the widgets will bedescribed in detail. Although reference is made to elements and featuresof particular icons and widgets, e.g., the RHS icon 730A, 730A′ and theCDM and RHS widgets 740, 760, those of skill in the art will appreciatethat the described elements and features are not limited to theseparticular icons and/or widgets. In addition, labeling of some elementsin the Figures is omitted for clarity.

As shown in FIG. 7A, the CDM widget 740 may comprise a visualrepresentation 744 corresponding to the forks (e.g., 156A, 156B in FIG.1A), including a numerical indication 747 of a current position of thecarriage assembly (144 in FIG. 1A), e.g., a current fork height (“4in”), and a current sensed or detected load weight 748 (“0 lbs”). Thecurrent fork height may also be indicated by a position of a pointer 749along a scale 742, which may comprise a plurality of tick marks (notseparately labeled) corresponding to height increments from, forexample, 0 inches to a maximum lift height for the vehicle 100. The CDMwidget 740 may also comprise a fork tilt indicator 745 and a forkcentering indicator 746. The fork tilt indicator 745 in FIG. 7Aindicates that the forks are currently level, while the fork tiltindicator 745′ in FIG. 7G indicates that the tips of the forks aretilted up. The fork tilt indicator 745 may similarly indicate that thetips of the forks are tilted down (not shown). The fork centeringindicator 746 may indicate that the forks are positioned to the left orright of a centerline of the vehicle 100 (not shown).

Data related to the detected load weight and the current fork height,tilt, and/or centering may be obtained as described herein and providedto the CDM widget 740 for display. For example, the processor of thecontrol module 226 is in communication with one or more vehicle controlmodules, sensors, etc. (e.g., 232), across the vehicle network system236, via the monitoring I/O module 230, or a combination thereof (FIG.2B). After extraction of the relevant information by the processor ofthe control module 226, the CDM widget 740 provides visualrepresentations corresponding to each parameter.

As shown in FIG. 7B, the RHS feature of the vehicle 100 has been turnedon or activated via the RHS icon 730A′, as indicated by the underlining735 and/or other visual indicator. The RHS icon 730A′ may be activatedusing touch gesture commands, using one or more of the control elements164A-164F in the vehicle operator control section 310 (FIG. 3), or usingone or more of the physical control elements in the control panel 126(FIG. 1B), such as the rotary control knob 162 (FIG. 1B) or a triggerswitch (not shown) as described herein. For example, the operator mayuse the up, down, right, and left buttons 164A-164D to navigate to theRHS icon 730A (FIG. 7A) and pressing the enter button 164E to activatethe RHS icon 730A′ (FIG. 7B). The operator may similarly turn the rotarycontrol knob 162 or 164F to the right or left to navigate to the RHSicon 730A and depress the rotary control knob 162, 164F to activate theRHS icon 730A′. When the control elements 164A-164F and/or the rotarycontrol knob 162, 164F are used, the display screen 600 may include afocus area or focus state, such as an outline box or highlightedbackground (not shown), to visually indicate a current location of acursor or a current selection, which assists the operator in navigatingto the desired portion of the display screen 600. As noted above, afterthe RHS icon 730A′ is activated, the RHS widget 760 is locked into alocked widget space, e.g., the first widget space 606 in FIG. 7B.

The RHS widget 760 may comprise a first menu portion 761, a sub-menuportion 762, and a pallet presence indicator 763, as shown in FIG. 7B.As described herein, the first menu portion 761 displays informationrelated to an option selected from a first menu 764 (FIG. 7D), and thesub-menu portion 762 may be used to display and select additionaloptions corresponding to the option selected in the first menu 764. Insome embodiments, as shown in FIG. 7B, activation of the RHS icon 730A′allows the first menu portion 761 to be displayed. In one embodiment,after the RHS icon is activated, the first menu portion is displayedupon activation of the first menu portion by the operator, as notedbelow. This feature ensures that the operator receives the most relevantinformation at the correct time with the least operator input. It alsoprevents the first menu portion 761 from being inadvertently activatedwhen the RHS function has not been activated via activation of the RHSicon.

The operator may access the first menu 764 by activating the first menuportion 761 using one or more touch gestures and/or the one or morecontrol elements in the vehicle operator control section 310 (FIG. 3) orthe control panel 126 (FIG. 1B). For example, the operator may activatethe first menu portion 761 via a touch gesture, e.g., by touching ortapping within the area encompassed by the box with dashed lines around“Stacker Pallets” at the top of the RHS widget 760 in FIG. 7B, or byperforming an equivalent function using one or more physical controlelements. An arrow or other visual indication (not labeled) within thefirst menu portion 761, e.g., to the right of the text “StackerPallets,” may indicate that additional options are available forselection, e.g., via the first menu 764.

As shown in FIG. 7D, the display screen 600 then displays the first menu764 comprising one or more options available for selection. The firstmenu 764 may be displayed in a variety of formats, such as a list, asidebar (not shown), or a scroll wheel (not shown). An optionalindicator 764 a may appear adjacent to the currently selected option,e.g., “Stacker Pallets.” In some embodiments, the first menu 764 may bedisplayed within the widget 760, as shown in FIG. 7D. In otherembodiments, the first menu 764 may be displayed in a separate windowthat is temporarily superimposed over one or more of the widget spaces.For example, as shown in FIG. 7C, a window 770 may be displayed over aportion of the first widget space 606.

In some embodiments, the options contained in the first menu 764 (alsoreferred to herein as a workspace zone menu) comprise a list ofavailable workspace zones. As described herein, one or more workspacezones may be stored in a memory of the vehicle 100. Each zone maycorrespond to, for example, a particular work site, warehouse, room, orother workspace, or area or portion thereof. The zones may be customizedby a vehicle owner or other end user based on the various zone(s) inwhich the vehicle 100 will be used. For example, the number of availablezones may be customized, and each zone may be assigned a zoneidentifier, e.g., a name (e.g., “Stacker Pallets” in FIG. 7B), a number,a color, or other identifying feature or combination thereof, which isdisplayed in the first menu portion 761 (also referred to herein as azone selection portion). In one particular embodiment, the operator mayonly activate the zone selection portion 761 if the RHS icon 730A′ hasbeen activated. In this embodiment, if the RHS icon 730A has not beenactivated, then touching a portion of the zone selection portion 761does not result in display of the first menu 764.

In other embodiments (not shown), the options listed in the first menu764 may comprise parameters or categories other than the zone. In oneparticular embodiment, the options may comprise a listing of racksdesignated by type, name, and/or number. For example, a first menu maycomprise a listing of racks such as: Fixed Rack #1; Portable Rack #1;Fixed Rack #2; Portable Rack #2. Each rack will have correspondingprogrammed rack heights and may be independent of a zone or location ofthe rack. In another particular embodiment, the options may comprise ajob type, e.g., pickup or put away.

With reference to the embodiment shown in FIG. 7D, the operator mayselect one of the options displayed in the workspace zone menu 764 oralter the display of the options using one or more touch gestures and/orone or more physical control elements in the vehicle operator controlsection 310 or the control panel 126 (FIG. 1B). For example, theoperator may touch or tap the name of the desired workspace zone, e.g.,“Freezer,” on the display screen 600 to select the workspace zone. Insome embodiments, the workspace zone menu 764 may comprise additionalzones located above and/or below the currently displayed zones. Byswiping or sliding a finger along the display screen 600 over the namesof the zones or near the indicator 764 a, the operator may scrollthrough the available zones. When the operator makes selections usingone or more of the physical control elements, the display screen 600 mayuse the focus area or state (not shown) to visually indicate the currentcursor location or current selection. For example, a background of thezone selection portion 761, such as the area encompassed by the box withdashed lines around the text “Stacker Pallets” in FIG. 7B, may becomehighlighted or shaded (not shown) to indicate that the zone selectionportion 761 is the current selection. The focus state may also include,for example, an outline box around the current selection.

Following selection of the desired option in the workspace zone menu764, the display screen 600 reverts back to a display of the RHS widget760 with the new selected workspace zone. For example, if the operatorselects “Freezer” in the workspace zone menu 764 shown in FIG. 7D, thedisplay screen 600 changes to the display depicted in FIG. 7E, in whichthe zone selection portion 761′ now displays the zone identifiercorresponding to the selected “Freezer” zone.

In addition, as shown in FIG. 7H, one or more functions of each widgetmay also be accessed via a general menu 766, which may be displayedafter the operator touches or selects an appropriate portion of thewidget (not shown). The general menu 766 may be displayed within thewidget or within the same widget space (as shown) or over anotherportion of the display screen 600, such as over a portion of the secondwidget space 608 (not shown). The general menu 766 may comprise one ormore options related to individual functions in a multi-function widget,e.g., “Select Zone” (accesses the first menu 764) and “Pallet Presence”(accesses the pallet presence indicator 763). In particular, the generalmenu 766 for the RHS widget 760 may be used to select the desiredworkspace zone when the operator is using, for example, one or more ofthe physical control elements in the vehicle operator control section310 (FIG. 3) or the control panel 126 (FIG. 1B). The operator moves thefocus area over the outer periphery of the RHS widget 760 shown in FIG.7B and presses the enter button 164E or depresses the rotary controlknob 162 or 164F to display the general menu 766. The operator selectsthe “Select Zone” option in the same manner, after which the displayscreen 600 lists the available zones in the first menu 764, as shown inFIG. 7D. The operator may then select the desired workspace zone asdescribed.

With reference to FIG. 7B, the sub-menu portion 762 may be used toselect and display additional options that correspond to the optionselected in the first menu 764 (FIG. 7D). In some embodiments, theadditional options may comprise a plurality of programmed rack heights,and the sub-menu portion 762 (also referred to herein as a rack heightselection portion) may comprise one or more of a rack height identifier762 a and a sidebar 762 b comprising a plurality of tabs. The rackheight selection portion 762 may comprise, for example, the areaencompassed by the box with dashed lines around the text “Height 3, 85in.” and the tabs in FIG. 7B. As described herein, one or moreprogrammed rack heights may be stored in a memory of the vehicle 100 foreach workspace zone or rack in the first menu 764. Each programmed rackheight corresponds to a desired height of the carriage assembly 144(FIG. 1A) and may be customized by the end user. For example, the numberof available rack heights and height values may be customized.

The rack height identifier 762 a may comprise information related to acurrently displayed rack height, such as a name (“Height 3”), a number,a color, or other identifying feature or combination thereof. As shownin FIG. 7B, a numerical programmed rack height, e.g., “85 in.,” mayoptionally be displayed in the rack height identifier 762 a in additionto or in place of the name of the selected rack height. Each tab in thesidebar 762 b corresponds to one programmed rack height. The sidebar 762b is defined by one or more tabs corresponding to one or more programmedrack heights in the workspace zone designated in the first menu portion761, e.g., the “Stacker Pallets” zone as shown in FIGS. 7B and 7G. Theadditional options displayed in the rack height selection portion 762are limited to those available for the particular option selected in theworkspace zone menu 764. For example, when the “Stacker Pallets” zone isselected, the additional options available in the rack height selectionportion 762 will comprise only the programmed rack heights for the“Stacker Pallets” zone.

When the first menu provides a listing of rack designations, theadditional options available for selection in the sub-menu portion maycomprise a plurality of programmed rack heights. Each rack designationin the first menu may have a corresponding set of one or more programmedrack heights in the sub-menu portion. For example, Fixed Rack #1 willhave a first set of programmed rack heights and Fixed Rack #2 will havea second set of programmed rack heights, wherein the first and secondsets may be different.

In some embodiments, the rack height selection portion 762 displaysinformation related to the last rack height selected by the operator. Inother embodiments, the rack height select portion 762 displaysinformation related to a default rack height, e.g., a next higher orlower available rack height based on a current position of the forkcarriage assembly 144 (FIG. 1A) and/or a previous direction of travel ofthe fork carriage assembly 144, both of which may be detected asdescribed herein. In some embodiments, a visual appearance of a tab 762b′ corresponding to the currently displayed rack height is altered toreflect its selection. For example, as shown in FIG. 7B, the tab 762 b′is elongated with respect to the other tabs in the sidebar 762 b.

In the illustrated embodiment, the operator may select a programmed rackheight via the sidebar 762 b using one or more touch gestures and/or oneor more physical control elements in the vehicle operator controlsection 310 (FIG. 3) or the control panel 126 (FIG. 1B). In general, theRHS feature is not available until the RHS icon 730A is activated. Whenthe RHS feature is off, the vehicle may be in “free” or “RHS-inactive”mode in which the operator may lower and lift the carriage assembly 144(FIG. 1A) to any height upon continuous activation of a lifting orlowering operation, for example, via actuation of a correspondingfingertip lever 172 (FIG. 1B). Thus, when the RHS icon 730A is notactivated, an operator may not activate the first menu portion 761, maynot access the first menu 764 and may not select a programmed rackheight via the sidebar 762 b. Following activation of the RHS icon 730Aand selection of a rack height using any of the methods describedherein, continuous activation of a lifting or lowering operation willcause the carriage assembly 144 to raise or lower to, and automaticallystop at, a selected rack height.

In one embodiment, the operator may select the desired rack height usingone or more touch gestures. For example, the operator may scroll throughthe tabs in the sidebar 762 b, such that when each tab is touched,information regarding that tab's corresponding rack height is displayedin the rack height identifier 762 a. Thus, an operator may touch a tabin the sidebar 762 b corresponding to the desired rack height or swipe afinger along the tabs and select the tab corresponding to the desiredrack height. Releasing touch of a selected tab in the sidebar 762Bcauses the corresponding programmed rack height to be selected. As shownin FIG. 7G, the operator has selected the fifth programmed rack height,which is reflected in the sidebar 762 b by elongated fifth tab 762 b″corresponding to the fifth programmed rack height. Upon selection of thetab 762 b″ corresponding to the desired rack height, one or moreadditional characteristic(s) related to the visual appearance of the tab762 b′ may be altered. For example, a background color or pattern of thetab 762 b″ may change, as shown in FIG. 7G. After the desired programmedheight is selected, the carriage assembly 144 will lift or lower to theselected rack height upon continuous activation of a lifting or loweringoperation via actuation of a corresponding fingertip lever 172 (FIG. 1B)or use of the multifunction control handle (not shown) by the operator.

In other embodiments, the rack height identifier 762 a may comprise ascroll wheel that allows the operator to scroll through the availableprogrammed rack heights by swiping or sliding his finger up or downalong the text displayed in the rack height identifier 762 a. The scrollwheel may wrap around and repeat when the operator reaches the lastoption at the top or bottom of the list. The scroll wheel defines asub-menu providing a listing of programmed rack heights corresponding tothe workspace zone designated in the first menu portion 761, which, inFIG. 7B, is the “Stacker Pallets” zone. In one embodiment, only a singleprogrammed rack height is visible at any given time in the rack heightidentifier scroll wheel. In other embodiments, two or more programmedrack heights are visible in the rack height identifier scroll wheel (notshown).

In further embodiments, the operator may use one or more physicalcontrol elements located in the vehicle operator control section 310(FIG. 3) to accomplish the same functions. For example, the operator mayuse the right or left direction buttons 164B, 164C to navigate to thesidebar 762 b and may use the up or down direction buttons 164A, 164D tonavigate through the tabs. The operator may press the enter button 164Eto select one of the tabs.

In yet further embodiments, the operator may use one or more physicalcontrol elements located in the control panel 126 (FIG. 1B) to select arack height. For example, with “Height 2” displayed in the rack heightidentifier 762 a, and the second tab elongated, the operator may actuatea trigger switch (not shown) provided on the control panel 126 once toselect the third tab 762 b′, after which a visual appearance of the tab762 b′ changes to reflect its selection (shown in FIG. 7B as beingelongated). The operator may toggle to “Height 4” (not shown) byactuating the trigger a second time, “Height 5” (see FIG. 7G) byactuating the trigger a third time, etc. Upon each actuation of thetrigger switch, the rack height identifier 762 a displays the nextavailable rack height and that rack height comprises a selected rackheight unless the trigger switch is actuated again, and the visualappearance of the corresponding tab 762 b′ is changed to reflect itsselection. To select a programmed rack height that is below thecurrently displayed height, e.g., “Height 2” (not shown), the operatoractuates the trigger until the top of the list of programmed rackheights is reached, after which the list wraps around and the operatormay begin toggling up the list from the lowest programmed rack heightuntil the desired height is reached. After the desired programmed heightis selected, the carriage assembly 144 will lift or lower to theselected rack height upon continuous activation of a lifting or loweringoperation by the operator.

In yet further embodiments, a trigger switch is provided on amultifunction control handle and when the RHS icon 730A is activated butno programmed height is selected, the display screen 600 may display theRHS widget 760. During lifting or lowering of the carriage assembly 144via the multifunction control handle, the height shown on the displayscreen will automatically change to a next available programmed rackheight. As the carriage assembly 144 is moving, the operator may selectthe next available programmed rack height, and the carriage assembly 144will stop at the selected rack height. For example, following activationof the RHS icon 730A′ and selection of the “Stacker Pallets” zone, theoperator begins a lifting operation without first choosing a programmedrack height. During the continuous lifting operation and while thecarriage assembly 144 is between racks, the operator actuates thetrigger switch (not shown) when the operator wishes for the carriageassembly 144 to stop at the next available programmed rack height, andthe carriage assembly 144 will stop at that next available programmedrack height, e.g., the fifth programmed height in FIG. 7G.

In all embodiments, a visual appearance of one or more portions of thevisual depiction of the first menu 764, the first menu portion 761 andthe options contained therein, and/or the sub-menu portion 762(including one or more of the rack height identifier 762 a and thesidebar 762 b) may be altered to indicate selection of a particularoption, e.g., a workspace zone, and/or a particular additional option,e.g., a rack height. In some embodiments, each option within the firstmenu 764 may be color-coded with a different color, and one or more ofthe items displayed in the first menu portion 761 and/or the sub-menumenu portion 762 may comprise a same color associated with thecorresponding option in the first menu 764.

For example, as shown in FIGS. 7B and 7E, a color of the zone selectionportion 761, e.g., a line 761 a, 761 a′ beneath the zone identifier andthe arrow (not labeled) to the right of the text in the zone selectionportion, may correspond to a color assigned to the currently selectedworkspace zone. One or more additional characteristics of the zoneselection portion 761, e.g., the text of the zone identifier, abackground area, etc. (not shown), may also be color-coded. Each zonemay be associated with a different color to allow the operator toquickly and easily identify and select the desired workspace zone. Theseassigned colors may also be reflected in the visual appearance of theoptions, e.g., the names of the zones, the lines beneath each zone (notlabeled), etc., contained in the workspace zone menu 764 (FIG. 7D). Inaddition, a color of one or more portions of the visual depiction of therack height selection portion 762, including the rack height identifier762 a and/or the sidebar 762 b, may correspond to a color assigned tothe selected zone. For example, the color of the text displayed in therack height identifier 762, 762 a′ and the color of the elongated tab762 b′ may correspond to the assigned color of the selected zone.

In some embodiments, the visual appearance of one or more portions ofthe CDM widget 750 and/or the RHS widget 760 may also change to indicatethat the carriage assembly 144 (FIG. 1A) has arrived at the selectedrack height. For example, one or more of a color, a thickness, etc. ofan outline 765 (FIG. 7G) of the RHS widget 760 may change to provide avisual confirmation to the operator that the carriage assembly 144 hasreached the desired/selected programmed rack height. In FIG. 7G, outline765 is shown darker and having an increased thickness or width toindicate to the operator that the carriage assembly 144 has reached theselected height of 129 inches, Height 5. In other embodiments, anaudible tone may sound as the carriage assembly 144 passes eachprogrammed rack height, and an audible tone or message may sound toindicate that the carriage assembly 144 has arrived at the selected rackheight. These features provide confirmation to the operator that theselected function has been successfully executed and that the vehicle100 is ready for the next operation, e.g., the carriage assembly 144 isat the expected position. In addition to the audible confirmation, thechange in the outline 765 of the RHS widget 760 provides a confirmationthat may be observed with a quick glance, which reduces operatordistraction and provides enhanced usability.

In addition, in some embodiments, a display of a portion of the CDMwidget 740 and/or the RHS widget 760 may change in real time as thecarriage assembly 144 raises or lowers. Movement of the carriageassembly 144 may be indicated by a corresponding upward or downwardmovement of the forks 744 and the pointer 749 along the scale 742 and bya corresponding increase or decrease in the numerical indication 747 ofthe rack height in the CDM widget 740. In addition, if a programmed rackheight has not been selected by a user prior to movement of the carriageassembly 144, the information displayed in the rack height selectionportion 762 may change as the forks approach each programmed rackheight. With reference to FIG. 7G, following selection of “Height 5” theoperator activates a continuous lifting operation causing the carriageassembly 144 to raise upwardly toward the corresponding programmed rackheight of 129 inches. This movement of the carriage assembly 144 may beindicated, in real time with the actual movement of the carriageassembly 144, by an upward movement of the forks 744 and the pointer 749along the scale 742 in the CDM widget 740 to a new positioncorresponding to the programmed height of “129 in.” and by the updatednumerical indication 747′ of the rack height, as shown in FIG. 7G. Inthe case where a programmed rack height is not selected prior tomovement of the carriage assembly 144, but instead, will be selected viaa trigger switch on a multifunction control handle during movement ofthe carriage assembly 144, the name of the rack height (e.g., “Height3,” “Height 4,” etc.) and the numerical rack height (e.g., “94 in.,”“109 in.,” etc.) displayed in the rack height identifier 762 a maychange as the carriage assembly 144 approaches each programmed rackheight. The location of the elongated tab 762 b′, 762 b″ may also changeas the carriage assembly approaches each programmed rack height.

The real-time display feature may be particularly helpful in embodimentsin which the operator selects a programmed rack height during a liftingor lowering operation. For example, during lifting and loweringoperations, the information displayed in the rack height selectionportion 762 of the RHS widget 760 indicates the next availableprogrammed rack height so that the operator may, for example, actuatethe trigger switch (not shown) to select the upcoming programmed rackheight. The operator may also use the location of the forks 744 alongthe scale 742 and the numerical indication 747 shown in the CDM widget740 to gauge the current position of the carriage assembly 144 and theproximity to the next programmed rack height.

As illustrated herein, the rack height selection feature may be used inconjunction with the zone selection feature, but those of skill in theart will appreciate that the two features may be used independently.Combined use of the two features helps to eliminate confusion betweensimilar, but slightly different, programmed rack heights that may existin different workspace zones. For example, different zones in a largewarehouse may comprise rack heights that are only inches apart. In theabsence of zones, it may be difficult for the operator to easilydetermine whether the forks have been raised to the correct height.Combined use of the two features also reduces the number of programmedrack heights through which the operator must search. For example, avehicle 100 that is used in several locations may store a large numberof programmed rack heights. Without zones, the operator must searchthrough all of the available rack heights, which adds time anddifficulty to the selection process and decreases operator productivity,particularly in environments required gloved operation. For embodimentswhere a trigger switch is provided and used, having correspondingprogrammed heights defined for separate workspace zones makes use of thetrigger switch during a lifting operation more usable as the operator ispresented only with corresponding programmed heights in the selectedworkspace zone in which the operator is working.

The pallet presence indicator 763 will now be described in more detail.As shown in FIG. 7B, the pallet presence indicator 763 comprises a loadpresence indicator 763 a and a load weight indicator 763 b and providesa visual indication of a presence or an absence of a detected load on,for example, the forks 156A (FIG. 1A). The pallet presence indicator 763may be displayed within the RHS widget 760, as shown in FIG. 7B.Alternatively, the pallet presence indicator 763 may be implemented as aseparate widget and/or icon (not shown). One or more sensors 232 (FIG.2B), such as a pressure transducer in a hydraulic cylinder (not shown)of the load handling assembly 140 (FIG. 1A), may sense a weight of aload 116 on the forks 156A. The control module 226 extracts from themonitoring input/output (I/O) module 230 (FIG. 2B) information receivedfrom the sensor(s) and provides this information for display on thedisplay screen 600 via the pallet presence indicator 763.

As shown in FIG. 7B, when no load is detected, the load presenceindicator 763 a contains a dashed outline of a box, and the load weightindicator 763 b displays a notification, such as displaying the text“Empty.” In addition, when no load is detected, the current detectedload weight 748 in the CDM widget 740 may also display “0 lbs.”

In FIGS. 7F and 7G, a load of 2,300 pounds is detected, as reflected inthe pallet presence indicator 763′. The load presence indicator 763 a′comprises a solid box and the load weight indicator 763 b′ comprises adisplay of “2300” to reflect the presence of a detected load weighing2,300 pounds. The current load weight 748′ in the CDM widget 740 hasalso been changed to display “2300 lbs.” Also as shown in FIGS. 7F and7G, the RHS feature may be used in conjunction with a load offsetfeature. For example, upon detection of a load on the forks, the loadoffset feature causes the fork carriage to stop at a slightly higherpoint (as compared to unloaded forks). This height difference may bereflected in the programmed height displayed in the rack heightidentifier 762. For example, the numerical programmed rack heightdisplayed in the rack height identifier 762 a for “Height 3” isincreased from “85 in.” in FIG. 7B (no load) to “94 in.” in the rackheight identifier 762 a′ in FIG. 7F (a detected load of 2,300 pounds) toreflect the increased height needed to ensure that the load, e.g., apallet, and the loaded forks will clear the rack. In addition, anumerical programmed rack height for “Height 5” may be “120 in.” forunloaded forks (not shown), but because a 2,300 pound load is detected,the rack height identifier 762 a″ displays a programmed rack height of“129 in.,” as shown in FIG. 7G.

However, some loads (typically <500 pounds) may be too light forautomatic detection by the one or more pressure sensors, causing thecontrol module 226 (FIG. 2B) to incorrectly indicate the absence of adetected load. As discussed herein, when the load is not properlysensed, the programmed rack height is not adjusted to accommodate theloaded forks, and one or more of the vehicle's features may not functionproperly. In these situations, the pallet presence indicator 763comprises an override function that permits the operator to manuallyindicate the presence of a load by activating a portion of the palletpresence indicator 763. For example, when the operator knows that a load116 is present on the forks 156A (FIG. 1A) but the pallet presentindicator 763 incorrectly indicates the absence of a load (FIG. 7B), theoperator may activate the override function by touching, tapping,clicking, or otherwise activating the pallet presence indicator 763. Insome embodiments, a portion of the display screen 600 corresponding tothe pallet presence indicator 763, e.g., an area enclosed by the ovalshape, may comprise a touch-sensitive region or “button.”

As shown in FIG. 71, the override function has been activated by theoperator, for example, by touching and releasing the area on the screendefining or otherwise activating the pallet presence indicator 763 inFIG. 7B. One or more characteristics of the pallet presence indicator763″ may change to reflect activation of the override function. Forexample, a background color and/or pattern within the pallet presenceindicator may change, as shown in FIG. 71. In addition, the loadpresence indicator 763 a″ comprises a solid box and the load weightindicator 763 b″ displays a notification, such as “Loaded,” to reflectthat the override function has been activated. The programmed rackheight displayed in the rack height identifier 762 a′ is also updated to94 in. to ensure that the loaded forks clear the rack. In someembodiments, the pallet presence indicator 763″ will reset to “Empty”(FIG. 7B) when the fork carriage reaches the programmed rack height,unless a load is sensed. When a load is sensed, (e.g., as shown in FIGS.7F and 7G), the override function may be disabled, and the palletpresence indicator 763″ will reset to “Empty” (FIG. 7B) only when noweight is detected.

With reference to FIGS. 7F and 7G, several additional features of theCDM widget 740 will be described in detail. In addition to providinginformation about the detected load weight and current fork height,tilt, and centering, the CDM widget 740 may also provide a visualindicator of a maximum lift height based on a detected load. When a load116 is present on the forks 156A, 156B (FIG. 1A), the vehicle 100typically has a maximum lift height to which the carriage assembly 144(FIG. 1A) should be raised for the weight of that particular load. Thecontrol module 226 (FIG. 2B) may determine a maximum lift height for theload based on a variety of parameters, such as the maximum lift heightof the vehicle, a maximum lift weight capability of the vehicle, acurrent fork tilt, etc. A portion of the scale 742, e.g., areas 742 a,742 b, as shown with dashed lines, may be color-coded to provide avisual indication of lift restrictions.

When no load is detected or the detected load requires no lift heightrestrictions, both areas 742 a, 742 b of the scale 742 may comprise auniform, default color, e.g., green (not shown), to provide a highlyvisible indication to the operator that all lift heights are within thelift capacity of the vehicle 100. In some embodiments, the CDM widget740 may comprise an indicator (not shown) representing a percentage ofcapacity, e.g., an indication that the carriage assembly 144 has beenraised to 80% of the determined maximum lift height.

Upon detection of a load requiring a lift height restriction, thecontrol module 226 (FIG. 2B) may change a color of one or more portionsof the CDM widget 740, in which the color(s) provide the operator with avisual indicator of the maximum lift height for that load. For example,as shown in FIGS. 7F and 7G, a load of 2,300 pounds is detected, which,in the illustrated embodiment, requires a lift height restriction. Aportion, e.g., area 742 a, of the scale 742 may remain, for example,green, to indicate that lift heights within this area are within thelift capacity of the vehicle 100. Another portion, e.g., area 742 b, ofthe scale 742 may be changed to another color, such as yellow or red(not shown), to provide a highly visible indication to the operator thatlift heights within area 742 b of the scale 742 exceed the lift capacityof the vehicle 100. In some embodiments (not shown), a color of one ormore portions of the visual representation corresponding to the forks744 and/or the pointer 749 may also change based on whether the forks156A are at a lift height that is within the lift capacity of thevehicle 100 or that has exceeded the lift capacity of the vehicle 100.In other embodiments, the control module 226 (FIG. 2B) may limit orrestrict operation of the vehicle 100, e.g., vehicle speed andacceleration, etc. In further embodiments, a numerical indication of themaximum lift height (not shown) may be placed on the scale 742, e.g., atthe junction between areas 742 a, 742 b.

When the detected load weight exceeds a maximum lift capacity of thevehicle 100, the entire scale 742, including areas 742 a and 742 b, maycomprise a different uniform color, e.g., red (not shown), to provide ahighly visible indication to the operator that the current load shouldnot be lifted to any height. In this situation, the control module 226may allow very limited movement of the vehicle 100, e.g., operation at aspeed below a certain threshold or over a predetermined distance, andmay optionally completely disable operation of the vehicle 100.

In some embodiments, a color-coded message (not shown) may be displayedon the display screen 600 to notify or warn the operator that, forexample, a determined maximum lift height for the detected load has beenexceeded, the detected load exceeds a determined maximum lift capacityof the vehicle, and/or that the forks 156A (FIG. 1A) are nearing thedetermined maximum lift height. In other embodiments, the control module226 may trigger one or more audible and/or visual warnings, such as aspoken warning, audible tones, flashing lights on the display screen 600or the vehicle 100, etc., upon detection of one or more of the aboveconditions. In all embodiments, when lift height restrictions exist, anaudible tone or message may sound when the carriage assembly 144approaches a maximum height and/or when the height of the carriageassembly 144 exceeds the maximum height.

FIGS. 8-11 are flowcharts illustrating computer-implemented processes todefine and control display of one or more items on a screen display of adisplay and processing device, e.g., the display and processing unit151. The computer-implemented processes can be carried out using, forexample, computer-readable hardware (e.g., computer-readable hardwarememory, computer readable storage media, etc.) comprising computerinstructions (e.g., in the form of program code) that instruct aprocessor to implement the described computer-implemented process. Forexample, the processes illustrated in FIGS. 8-11 can be carried out bythe control module 226 (FIG. 2B). In this regard, the flowchartsdepicted in FIGS. 8-11 each outline an algorithm that is executed by theprocessor.

FIG. 8 is a flowchart illustrating a computer-implemented process 800 todefine and control display of a plurality of items, e.g., widgets, on ascreen display. The process begins at Step 810 in which the processordefines a plurality of widgets via execution of an application programcorresponding to each widget. Each widget comprises a visualrepresentation of a current state of an associated function of anindustrial vehicle. In Step 820, the processor controls display of asubset of the plurality of widgets on a portion of the screen displaydefining a plurality of widget spaces, and at Step 830, the processorcontrols display of an icon tray on the screen display comprising one ormore icons, wherein each of the one or more icons may be defined viaexecution of a corresponding application program. At least one of theicons corresponds to a respective one of the plurality of widgets. Asshown in FIG. 8, the process may continue to Step 840 in which theprocessor detects activation of the one icon corresponding to the onewidget, and in response to detecting the activation of the one icon,locks the respective one widget in position in a locked widget space inStep 850.

FIG. 9 is a flowchart illustrating a computer-implemented process 900 todefine and control display of one or more items, e.g., widgets, on ascreen display. The process begins at Step 910 in which the processordefines one or more widgets. Each widget comprises a visualrepresentation of a current state of an associated function of anindustrial vehicle. At Step 920, the processor controls display of atleast one of the one or more widgets on a portion of the screen displaydefining one or more widget spaces, and at Step 930, the processorcontrols display of an icon tray on the screen display comprising one ormore icons. At least one of the icons corresponds to a respective one ofthe one or more widgets. The processor detects activation of the oneicon corresponding to the one widget at Step 940, and in response todetecting the activation of the one icon, allows a first menu portion ofthe one widget to be displayed in Step 950. At Step 960, the processorcontrols display of a first menu associated with the one widget.

FIG. 10 is a flowchart illustrating a computer-implemented process 1000to define and control display of one or more items on a screen display.The process begins at Step 1010 in which the processor defines one ormore widgets. Each widget comprises a visual representation of a currentstate of an associated function of an industrial vehicle. At Step 1020,the processor controls display of a rack height select (RHS) widget on aportion of the screen display defining one or more widget spaces. TheRHS widget comprises a portion, e.g., an outline, that changes stateupon a related vehicle function being completed, e.g., a carriageassembly of the industrial vehicle reaching a desired height.

FIG. 11 is a flowchart illustrating a computer-implemented process 1100to define and control display of a plurality of items on a screendisplay. The process begins at Step 1110 in which the processor definesa plurality of widgets. Each widget comprises a visual representation ofa current state of an associated function of an industrial vehicle. AtStep 1120, the processor controls display of a subset of the pluralityof widgets on a portion of the screen display defining a plurality ofwidget spaces, and at Step 1130, the processor controls display of anicon tray on the screen display comprising one or more icons. At leastone of the icons corresponds to a respective one of the plurality ofwidgets. The processor detects activation of the one icon correspondingto the one widget at Step 1140, and in response to detecting theactivation of the one icon, moves the respective one widget to apredefined widget space in Step 1150. At Step 1160, the processor movesthe respective one widget from the predefined widget space in responseto an operator command to move the widget away from the predefinedwidget space, and at Step 1170, the processor moves the one widget backto the predefined widget space in response to a command related to avehicle operation.

In addition to, or in place of, the use of one or more touch gestures orphysical control elements in the vehicle operator control section 310(FIG. 3) or the control panel 126 (FIG. 1B), the operator may make oneor more selections using a voice control system (not shown), examples ofwhich are described more fully in U.S. Pat. No. 7,017,689, the entiretyof which is hereby incorporated by reference herein. The operator may beequipped with a headset (not shown), and/or the display unit 151 or aportion of the control panel 126 may comprise a microphone (not shown).The voice control system is programmed to receive and recognize one ormore predetermined verbal commands from the operator. The vehiclecontrol system then translates each verbal command into a signal forprocessing by, for example, the control module 226 and/or one or morecontrol modules or controllers 238 (FIG. 2B), which transmits anappropriate output command to control operation of the display unit 151(FIG. 3) and/or the vehicle 100.

For example, receipt of the verbal command ACTIVATE RHS ICON or ACTIVATERHS WIDGET may activate the RHS icon 730A and move the RHS widget 760(FIG. 7B) to a predefined widget space in a manner similar to themovement of the RHS widget 760 upon activation of the RHS icon 730Ausing one or more touch gestures or physical control elements, asdescribed herein. Receipt of the verbal commands SELECT ZONE or SELECTRACK HEIGHT may activate or cause the display of the zone selectionportion 761 or the rack height selection portion 762, respectively, ofthe RHS widget 760 in a manner similar to the activation or displayfollowing the use of one or more touch gestures or physical controlelements, as described herein.

Referring now to FIG. 12, a schematic block diagram illustrates anexemplary computer system 800 for implementing the control module 226 ofFIG. 2B. The exemplary computer system 800 comprises one or more(hardware) microprocessors 810 and corresponding (hardware) memory 820(e.g., random access memory and/or read only memory) that are connectedto a system bus 830. Information may be passed between the system bus830 and an optional data bus 850 by a suitable bridge 840. The data bus850 is used to interface peripherals with the one or moremicroprocessors 810, such as storage 860 (e.g., solid state hard diskdrive); removable media storage device(s) 870 (e.g., flash drives,etc.); I/O devices 880 (e.g., the graphical user interface module of theservice module 220 of FIG. 2B, a universal serial bus (USB) interface,etc.); and one or more adapters 890. The adapters 890, where provided,allow the microprocessor 810 to communicate across one or more of thevehicle network systems (e.g., 236 of FIG. 2B). In this regard, exampleadapters 890 may comprise Bluetooth®, Ethernet, CAN bus, RS422, LIN Bus,WiFi, cellular, etc.

This list of peripherals is presented by way of illustration, and is notintended to be limiting. Other peripheral devices may be suitablyintegrated into the computer system 800. The memory 820, storage 860,removable media insertable into the removable media storage 870, orcombinations thereof may be used to implement the methods,configurations, interfaces and other aspects set out and describedherein.

The microprocessor(s) 810 control operation of the exemplary computersystem 800. Moreover, one or more of the microprocessor(s) 810 executecomputer readable code that instructs the microprocessor(s) 810 toimplement the methods and processes herein. The computer readable codemay be stored for instance, in the memory 820, storage 860, removablemedia storage device(s) 870, or other suitable tangible storage mediumaccessible by the microprocessor(s) 810. The memory 820 may alsofunction as a working memory, e.g., to store data, an operating system,etc.

The methods and processes herein may be implemented as amachine-executable method executed on a computer system, e.g., one ormore general or particular computing devices such as the processingdevices 202 of FIGS. 2A and 2B, on a system 800 of FIG. 12, orcombinations thereof. In this regard, the methods and processes hereinmay be implemented on a computer-readable storage device (e.g.,computer-readable storage hardware) that stores machine-executableprogram code, where the program code instructs a processor to implementthe described method/process. The methods and processes herein may alsobe executed by a processor coupled to memory, where the processor isprogrammed by program code stored in the memory, to perform thedescribed method.

Computer program code for carrying out operations for any aspect orembodiment of the present disclosure may be written in any combinationof one or more programming languages. The program code may execute fullyor partially on the computer system 800. In the latter scenario, theremote computer may be connected to the computer system 800 through anytype of network connection, e.g., using the network adapter 890 of thecomputer system 800. In implementing computer aspects of the presentdisclosure, any combination of computer-readable medium may be utilized.The computer-readable medium may be a computer readable signal medium, acomputer-readable storage medium, or a combination thereof. Moreover, acomputer-readable storage medium may be implemented in practice as oneor more distinct mediums.

A computer-readable storage medium is a tangible device/hardware thatmay retain and store a program (instructions) for use by or inconnection with an instruction execution system, apparatus, or device,e.g., a computer or other processing device set out more fully herein.Notably, a computer-readable storage medium does not encompass acomputer-readable signal medium. Thus, a computer readable storagemedium, as used herein, is not to be construed as being transitorysignals per se, such as radio waves or other freely propagatingelectromagnetic waves through a transmission media. Specific examples ofthe computer-readable storage medium may include, but are not limitedto, the following: a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory(EPROM), Flash memory, or any suitable combination of the foregoing. Inparticular, a computer-readable storage medium comprisescomputer-readable hardware such as a computer-readable storage device,e.g., memory. As used herein, a computer-readable storage device andcomputer-readable hardware are physical, tangible implementations thatare non-transitory.

By non-transitory, it is meant that, unlike a transitory propagatingsignal per se, which will naturally cease to exist, the contents of thecomputer-readable storage device or computer-readable hardware thatdefine the claimed subject matter persists until acted upon by anexternal action. For instance, program code loaded into random accessmemory (RAM) is deemed non-transitory in that the content will persistuntil acted upon, e.g., by removing power, by overwriting, deleting,modifying, etc. Moreover, since hardware comprises physical element(s)or component(s) of a corresponding computer system, hardware does notencompass software, per se. The terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting of the disclosure. As used herein, the singular forms “a,”“an,” and “the” are intended to include the plural forms as well, unlessthe context clearly indicates otherwise. It will be further understoodthat the terms “comprises” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The description of the present disclosure has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited only to the embodiments in the form disclosed.Many modifications and variations will be apparent to those of ordinaryskill in the art without departing from the scope and spirit of theinvention.

Having thus described the invention of the present application in detailand by reference to embodiments thereof, it will be apparent thatmodifications and variations are possible without departing from thescope of the invention defined in the appended claims.

What is claimed is:
 1. A processing device comprising a graphical userinterface in an industrial vehicle, the processing device comprising: ascreen display; memory storing executable instructions; and a processorin communication with the memory, wherein the processor when executingthe executable instructions: defines one or more widgets, each widgetcomprising a visual representation of a current state of an associatedfunction of the industrial vehicle; controls display of at least one ofthe one or more widgets on a portion of the screen display defining oneor more widget spaces; controls display of an icon tray on the screendisplay comprising one or more icons, wherein at least one of the one ormore icons corresponds to a respective one of the one or more widgets;detects activation of one of the one or more icons corresponding to therespective one widget; in response to detecting the activation of theone icon, allows a first menu portion of the respective one widget to bedisplayed; and controls display of a first menu associated with therespective one widget.
 2. The processing device of claim 1, wherein theprocessor when executing the executable instructions: in response todetecting the activation of the one icon, allows a first menu portion ofthe respective one widget to be activated; detects activation of thefirst menu portion; and in response to detecting the activation of thefirst menu portion, controls display of the first menu associated withthe respective one widget.
 3. The processing device of claim 1, whereinthe processor when executing the executable instructions: further inresponse to detecting the activation of the one icon, locks therespective one widget in position in a first widget space on the screendisplay.
 4. The processing device of claim 3, wherein the processor whenexecuting the executable instructions: defines a plurality of widgetsand a plurality of widget spaces; and further in response to detectingthe activation of the one icon: shifts the remaining one or more widgetsto the one or more remaining widget spaces.
 5. The processing device ofclaim 1, wherein the processor when executing the executableinstructions: defines the icon tray as a separate portion of the screendisplay from the one or more widget spaces, the icon tray being spacedapart from the one or more widget spaces.
 6. The processing device ofclaim 1, wherein: the screen display comprises a touch screen displaythat receives touch gesture commands from a vehicle operator; and theprocessor when executing the executable instructions: shifts a positionof one or more of the widgets on the touch screen display followingdetection of a touch gesture on the touch screen display.
 7. Theprocessing device of claim 1, wherein: the screen display comprises atouch screen display that receives touch gesture commands from a vehicleoperator; and the first menu portion of the respective one widget isactivated by a vehicle operator touching or selecting the first menuportion.
 8. The processing device of claim 7, wherein: the first menucomprises a list, a sidebar, or a scroll wheel; and a display of optionsin the first menu is altered by one of a tap gesture, a swipe gesture,or a slide gesture on the touch screen display, the options within thefirst menu being color-coded with a different color.
 9. The processingdevice of claim 1, wherein the processor when executing the executableinstructions: defines a plurality of sub-menus, each sub-menucorresponding to a particular option within the first menu, wherein onesub-menu is displayed on the screen display after the correspondingoption within the first menu has been selected.
 10. The processingdevice of claim 9, wherein the processor when executing the executableinstructions: color codes at least a portion of the one sub-menu using asame color associated with the corresponding option within the firstmenu.
 11. The processing device of claim 9, wherein one or more of thefirst menu or the sub-menus are displayed within the respective onewidget.
 12. The processing device of claim 9, wherein one or more of thefirst menu or the sub-menus are displayed in a separate window that istemporarily superimposed over one or more of the widget spaces.
 13. Theprocessing device of claim 1, wherein the processor when executing theexecutable instructions: defines the respective one widget as a rackheight select (RHS) widget, the RHS widget comprising: a workspace zonemenu defining the first menu, the workspace zone menu comprising aplurality of workspace zones, each workspace zone having a correspondingsub-menu comprising a plurality of stored rack heights associated withthe workspace zone; and a load presence indicator.
 14. The processingdevice of claim 1, further comprising: a vehicle network systemconnecting the processor to at least one vehicle network bus, whereinthe processor extracts a current position of a carriage assembly and acurrent sensed load weight, wherein the processor when executing theexecutable instructions: defines one of the one or more widgets as acapacity data monitoring (CDM) widget, the CDM widget comprising avisual representation of the current position of the carriage assemblyand the current sensed load weight.
 15. The processing device of claim1, further comprising a vehicle operator control section comprising oneor more physical input control elements, wherein the one or morephysical input control elements are used to make selections on thescreen display.
 16. The processing device of claim 15, wherein the oneor more physical input control elements comprise at least one of afive-button control, a trigger switch, or a rotary control knob.
 17. Theprocessing device of claim 1, wherein: the screen display comprises atouch screen display that receives touch gesture commands from a vehicleoperator; and the processor when executing the executable instructions:determines if a speed of the industrial vehicle is below a thresholdspeed; and changes one or more of the one or more widgets on the touchscreen display following detection of a touch gesture on the touchscreen display and if the speed of the industrial vehicle is below thethreshold speed.
 18. The processing device of claim 1, wherein theprocessor when executing the executable instructions: further inresponse to detecting the activation of the one icon, moves therespective one widget to a predefined widget space.